lkml.org 
[lkml]   [2003]   [Jun]   [6]   [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
Florian Weimer <fw@deneb.enyo.de> writes:

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

Some more data points:

o 2.5.70 fails as well.

o ext2 on 2.5.70, too.

o Above errors are definitely critical. 8-(

o It seems as if the kernel assumes that a file is a directory. (At
least after running 2.5.70/ext2 for a while, e2fsck had some
problems regenerating a proper file system structure and marked a
few files as directories.)

o Vanilla 2.4.20 is rock solid on the same hardware (no more file
system corruption after downgrade).
-
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:36    [W:1.351 / U:0.000 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site