[lkml]   [2002]   [May]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Ext3 errors with 2.4.18
"Udo A. Steinberg" wrote:
> Hi,
> With Linux 2.4.18, I'm getting multiple of the following error:
> EXT3-fs error (device ide0(3,2)): ext3_readdir: bad entry in directory #1966094:
> rec_len % 4 != 0 - offset=0, inode=3180611420, rec_len=53134, name_len=138
> Can someone decipher this?

That's random junk. Heaven knows. It could have come
from anywhere in the kernel. Including ext3, of course.

When you see this sort of thing you should immediately
take the machine down, because the corruption could be
only in-memory. The longer the machine stays up, the
better the chance that the corruption will go to disk.

And with ext3, the best way to take the machine down
is to pull the power plug. Normal shutdown tools will
sync the disks, which you don't want to happen.

Then reboot with `init=/bin/sh' and force a fsck against
all filesystems.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:25    [W:0.053 / U:5.296 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site