Messages in this thread | | | From | Andreas Dilger <> | Subject | Re: RAID, 2.4.2 and Buslogic | Date | Wed, 7 Mar 2001 01:20:51 -0700 (MST) |
| |
Jauder Ho writes: > My story is somewhat similar to what Dick Johnson has encountered except > this is with 2.4.2 running on a pentium 200. > > EXT2-fs error (device md(9,0)): ext2_add_entry: bad entry in directory > #343396: > inode out of bounds - offset=0, inode=343396, rec_len=12, name_len=1 > EXT2-fs error (device md(9,0)): ext2_write_inode: bad inode number: 12 > > EXT2-fs error (device md(9,0)): free_inode: reserved inode or nonexistent > inode > kernel BUG at inode.c:885!
Inode 12 is a perfectly valid inode number for any filesystem, so your ext2 superblock must have been corrupt (or zeroed out) at this point. The value for sb->u.ext2_sb.s_es->s_inodes_count must have been < 12 (likely zero), which would explain all of these errors. Strange.
I have posted (twice) a patch which would prevent the BUG from happening. Granted, it won't help your RAID/SCSI corruption problem (*). Please see
[PATCH] sanity checks for ext2 root inode
in l-k archives. I don't think this is in either Linus' or Alan's tree.
Cheers, Andreas
(*) in normal cases this prevents a small filesystem corruption from halting the system, but in your case, the BUG may have prevented larger corruption by halting the system before more damage was done? -- Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto, \ would they cancel out, leaving him still hungry?" http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |