Hi, I just want to reiterate that this problem is reliably reproducable. I
can cut power to the machine as many times as I want and XFS never
recovers. I can even do a "sync" beforehand and it still does not recover.
Furthermore, if I boot with a boot CD and attempt a mount, XFS recovers
fine (on all partitions).
For some reason my kernel is not able to recover from an improper
Attached is a log print generated by xfs_logprint -t off a boot CD as
Here's an xfs_info printout of the partition as well:
meta-data=/mnt/test isize=256 agcount=3, agsize=436820 blks
data = bsize=4096 blocks=1310460, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=0
naming =version 2 bsize=4096
log =internal bsize=4096 blocks=16384, version=1
= sectsz=512 sunit=0 blks
realtime =none extsz=65536 blocks=0, rtextents=0
On 22 Sep 2003, Steve Lord wrote:
> On Mon, 2003-09-22 at 16:16, Cory Visi wrote:
> > On Mon, 22 Sep 2003, Net Llama! wrote:
> > >
> > > 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?
> Recovery is completely local to the kernel, and should not be affected
> by user space in anyway. If you have a way of getting to the device
> before it mounts can you run xfs_logprint -t on it? Since this is your
> root it may be a little difficult.
> The output looks a little like you have a hole in your log which is
> not being coped with.
Description: Text document