Re: XFS oops, kernel 2.4.30 w/grsecurity

[Nathan Scott]

On Mon, Jun 06, 2005 at 02:47:02PM +0200, Marek Materzok wrote:
> Jun  6 11:40:08 lucifer kernel: Filesystem "ide0(3,6)": XFS internal error xfs_btree_check_lblock at line 222 of file xfs_btree.c.  Caller 0xc01ed58d
> Jun  6 11:40:08 lucifer kernel: c9871750 c01efc41 c0374857 00000001 d71ffc00 c037484b 000000de c01ed58d 
> Jun  6 11:40:08 lucifer kernel:        c8bd4f80 d76b2940 00ca1740 00000000 00000008 00000000 c987178c cf416124 
> ...
> Then, the /home partition (/dev/hda6) was disabled, and every access to
> it ended with EIO. A reboot fixed the problem - the filesystem was
> rebuilt and mounted correctly. Nothing like this happened ever to my XFS
> filesystems.

This isn't an oops, its what XFS does when it detects on-disk
metadata corruption - it shuts down the filesystem, reports a
kernel stack trace and some other diagnostics, and returns EIO
on subsequent accesses to the filesystem until the problem is
resolved and the filesystem is mounted once more.

cheers.

-- 
Nathan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/