Re: EXT2-fs error with 2.4.4 (using CVS)

Andreas Dilger (adilger@turbolinux.com)
Mon, 7 May 2001 22:45:59 -0600 (MDT)

Federic Meunier writes:
> ==> /var/log/syslog <==
> May 8 00:25:52 pervalidus kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir: bad entry in
> directory #162813: directory entry across blocks - offset=92, inode=451111, rec_len=16404,
> name_len=9
> May 8 00:25:52 pervalidus kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir: bad entry in
> directory #162813: directory entry across blocks - offset=92, inode=451111, rec_len=16404,
> name_len=9
>
> When CVS finished, I received the following error:
>
> May 8 01:11:29 pervalidus kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir: bad entry in
> directory #162813: directory entry across blocks - offset=92, inode=451111, rec_len=16404,
> name_len=9
> May 8 01:11:29 pervalidus kernel: EXT2-fs error (device ide0(3,3)): ext2_readdir: bad entry in
> directory #162813: directory entry across blocks - offset=92, inode=451111, rec_len=16404,
> name_len=9

Since it is always the same inode, I would say it is corrupt. You need to
run e2fsck to fix it. It looks like it is a single-bit error on the disk.
The rec_len=16404=0x4014. One (of many possible) valid rec_len would be
0x14=20. To be valid we need name_len <= rec_len <= block size.

Chances are, when you run e2fsck, it will fix this dirent, but the rest of
the directory entries in that block will be moved to lost+found.

I would suspect a hardware problem, to create a single-bit error (if it
is such).

Cheers, Andreas

-- 
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/