On Mon, 22 Sep 2003, Net Llama! wrote:
> On Mon, 22 Sep 2003, Cory Visi wrote:
>
> > > > I recently patched up my own custom 2.4.22 kernel with the 2.4.22 XFS
> > > > split patches. I am also using the 2.4.23-pre4 patch.
> > > >
> > > > To do a filesystem test, I basically just shut the machine off and
> > > > see if XFS recovers. Which I did. Instead of the system booting up, I
> > > > get
> > > > this:
> > > >
> > > > <normal kernel messages cut>
> > > > XFS mounting filesystem sd(8,1)
> > > > Starting XFS recovery on filesystem: sd(8,1) (dev: 8/1)
> > > > XFS: xlog_recover_process_data: bad clientid
> > > > XFS: log mount/recovery failed
> > > > XFS: log mount failed
> > > > Kernel panic: VFS: Unable to mount root fs on 08:01
> > >
> > > i recently had several power failures, and my UPS batteries failed,
> > > and as a result i had four 2.4.22 systems lose power, all recovered
> > > perfectly fine (several times). I think there must be something else
> > > going on with your setup.
> >
> > Ok, assuming this is the case, what kinds of things can cause a log
> > recovery to fail? Am I mounting it wrong in the bootloader? I'm
> > telling the kernel to mount read-only. Am I mounting with the wrong mount
> > options? Any help would be appreciated.
>
> Are you running the latest release of xfsprogs?
I'm not sure if it matters, but I'm running:
acl-2.2.13
attr-2.4.7
dmapi-2.0.8
xfsdump-2.2.13
xfsprogs-2.5.4
Do any of these affect the XFS recovery during a mount?
Thank you,
Cory Visi
|