Ext3 users - Jul 2004 - How to interpret corruption error message

(sort-of xposted from linux-kernel)

Hi,

I am wondering how to interpret this error message, which popped up on a
2.4.26 SMP x86 box two days ago:

EXT2-fs: corrupt root inode, run e2fsck
init_special_inode: bogus imode (37316)
EXT2-fs: corrupt root inode, run e2fsck
init_special_inode: bogus imode (37316)
EXT2-fs: corrupt root inode, run e2fsck

The problem is, the error message doesn't indicate *which* filesystem we
are talking about, and I have three mounted: 1 ext2 and 2 ext3.  The
ext2 is on a plain old pata disk and the two ext3 filesystems are on
software raid5 sata volumes.

I'm pretty much afraid to reboot the machine at this point, I have no
idea which FS I'm about to lose.  Any hints appreciated.

-jwb

On Jul 22, 2004  10:32 -0700, Jeffrey W. Baker wrote:
> I am wondering how to interpret this error message, which popped up on a
> 2.4.26 SMP x86 box two days ago:
> 
> EXT2-fs: corrupt root inode, run e2fsck
> init_special_inode: bogus imode (37316)
> EXT2-fs: corrupt root inode, run e2fsck
> init_special_inode: bogus imode (37316)
> EXT2-fs: corrupt root inode, run e2fsck
> 
> The problem is, the error message doesn't indicate *which* filesystem
we
> are talking about, and I have three mounted: 1 ext2 and 2 ext3.  The
> ext2 is on a plain old pata disk and the two ext3 filesystems are on
> software raid5 sata volumes.
The ext3 filesystems would report "EXT3-fs: ...", but yes it would be
good if ext3_error() and ext3_warning() would include the device name
or number.

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://members.shaw.ca/adilger/             http://members.shaw.ca/golinux/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<http://listman.redhat.com/archives/ext3-users/attachments/20040722/5e5a0262/attachment.sig>