lkml.org 
[lkml]   [2003]   [May]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [2.5.69] ext3 error: rec_len %% 4 != 0
From
Date
Andrew Morton <akpm@digeo.com> writes:

> Florian Weimer <fw@deneb.enyo.de> wrote:
>>
>> Sometimes, our 2.5 test machine (actually, it's a production machine,
>> please don't ask why we can't use 2.4 *sigh*) stops with an ext3 error
>> message. We have now activated proper logging, and that's what we
>> got:
>>
>> May 28 03:23:00 kernel: EXT3-fs error (device md0): ext3_readdir: bad entry in directory #16056745: rec_len %% 4 != 0 - offset=52, inode=431743, rec_len=37017, name_len=41

Another error message is the following one:

EXT3-fs error (device md0): ext3_readdir: bad entry in directory #12812298: directory entry across blocks - offset=0, inode=1308, rec_len=38720, name_len=225

Hmm.

> Falling back to ext2 for a while would be interesting.

I see the following messages with dmesg, but they appear to be
non-critical:

init_special_inode: bogus i_mode (67)
init_special_inode: bogus i_mode (177766)
init_special_inode: bogus i_mode (5)
init_special_inode: bogus i_mode (65)
init_special_inode: bogus i_mode (53664)
init_special_inode: bogus i_mode (5)

Are they related? They didn't appear with ext3.
-
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/

\
 
 \ /
  Last update: 2005-03-22 13:35    [from the cache]
©2003-2011 Jasper Spaans