This may account for my test xfs news server not surviving for more
than a week. But, the filesystem pretty much goes unrecoverable after
I am forced to reset the box:
kmem_alloc doing a vmalloc 241488 size & PAGE_SIZE 0 rval=0xf8829000
Start mounting filesystem: sd(8,17)
Starting XFS recovery on filesystem: sd(8,17) (dev: 8/17)
cmn_err level 1 Filesystem "sd(8,17)": xfs_inode_recover: Bad inode
log record, rec ptr 0xf5165fc0, dino ptr 0xf5091d00, dino bp
0xe2cb73c0, ino 121654813, total extents = -4746, nblocks = 16
XFS: log mount/recovery failed
XFS: log mount failed
Size 241488 doing a vfree 0xf8829000
Now xfs_check is spewing countless (with the block number increasing):
block 2/195770000 out of range
-tony
On 02-Dec-2000 Russell Cattelan wrote:
>
> Yes this is a know problem in the latest 2.4 kernels.
> It has been observed on other file systems as well not just XFS.
>
> I have do have a kernel with Jens elevator patch, that does
> appear to fix the starvation problem. Unfortunately it appears to
> either
> have problems itself or is exposing problems in the XFS code.
>
> Currently XFS kiobuf based io causes a lockup that eventually cause
> the
> kernel to through an NMI.
>
> Non kiobuf io causes pagebuf to panic under heavy load.
>
> I got this running late friday and haven't had much
> of a chance to investigate.
>
> Since this is a linux bug we are waiting for the official
> fix to show up in the linux tree.
>
> --
> Russell Cattelan
> cattelan@xxxxxxxxxxx
---
E-Mail: Tony Gale <gale@xxxxxxxxxxxxxxxxxx>
I cannot draw a cart, nor eat dried oats; If it be man's work I will do it.
The views expressed above are entirely those of the writer
and do not represent the views, policy or understanding of
any other person or official body.
|