public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.5.69] ext3 error: rec_len %% 4 != 0
Date: Fri, 06 Jun 2003 09:59:11 +0200	[thread overview]
Message-ID: <87smqn3acw.fsf@deneb.enyo.de> (raw)
In-Reply-To: <87znl45utw.fsf@deneb.enyo.de> (Florian Weimer's message of "Fri, 30 May 2003 17:15:55 +0200")

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

      reply	other threads:[~2003-06-06  7:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28  8:05 [2.5.69] ext3 error: rec_len %% 4 != 0 Florian Weimer
2003-05-28  8:25 ` Andrew Morton
2003-05-28  8:50   ` Florian Weimer
2003-05-28  8:59     ` Andrew Morton
2003-05-30 15:15   ` Florian Weimer
2003-06-06  7:59     ` Florian Weimer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87smqn3acw.fsf@deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox