On Fri, 21 May 2004, marat wrote:
> I have got some strange problem on Linux RH9 system, kernel 2.4.25
a kernel.org kernel?
> The XFS filesystem crashed with message :
> Filesystem "sd(8,33)": XFS internal error xfs_btree_check_lblock at
> line 222 of file xfs_btree.c. Caller 0xf89b695f
> f65ada4c f89b7ffa f8a14e7a 00000001 f6e78400 f8a14e6e 000000de f89b695f
> > ea6a6dcc e68ffe40 db68dd84 db68dd84 f89b8da5 d3a0d7a8 e3a8d1a0
> 0a05bb82 d87da000 db68dd84 00000000 00000000 f89b695f db68dd84
> Call Trace: [<f89b7ffa>] [<f8a14e7a>] [<f8a14e6e>] [<f89b695f>]
please run this through ksyumoops to get full backtrace information.
> xfs_force_shutdown(sd(8,33),0x8) called from line 1070 of file
> xfs_trans.c. Return address = 0xf8a05a5b
> Filesystem "sd(8,33)": Corruption of in-memory data detected. Shutting
> down filesystem: sd(8,33)
> Please umount the filesystem, and rectify the problem(s)
> I had to reboot system and run xfs_repair. it looks like xfs_repair does not
> fix all problems, I have tried to run it several times and every time had the
> same output.
this may be normal, the first thing repair does is unlink lost+found, and
then rediscovers everything in it. rename lost+found and try again,
things should be fine. if you still see unrepaired errors please
post the complete output of repair (or send directly to me if it's
> I attached output from xfs_repair command ( I had to edit file to make it
> readable ).
hm, what was unreadable?