[lkml]   [2002]   [May]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Ext3 errors with 2.4.18
On Monday 06 May 2002 18:25, 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


I experienced the same problem with ext3 + 2.4.18 on a RAID-1. Out of nowhere
the following error popped up in the syslog, no other surrounding error
messages. The fs was mounted read-only automatically. After reboot and fsck
there were /a lot/ of errors on the disk. Virtually all errors fsck knows I
think. :) After fsck ran multiple times on the disk, lost+found was filled
with stuff from all accross the disk, but other than that the fs seems to
have survived it.

May 14 01:24:41 kianga kernel: EXT3-fs error (device md(9,0)): ext3_readdir:
bad entry in directory
#2142115: rec_len %% 4 != 0 - offset=0, inode=4186379891, rec_len=16755,
May 14 01:24:51 kianga last message repeated 2 times


Oliver Feiler <kiza@(|||> / ( /
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:26    [W:0.055 / U:1.268 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site