From: Jan Kara <jack@suse.cz>
To: Andy Whitcroft <andyw@uk.ibm.com>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Subject: Re: 2.6.23-git18: ext2_check_page: bad entry in directory
Date: Wed, 24 Oct 2007 15:59:00 +0200 [thread overview]
Message-ID: <20071024135900.GC2652@duck.suse.cz> (raw)
In-Reply-To: <20071024131540.GV32058@shadowen.org>
Hello,
On Wed 24-10-07 14:15:40, Andy Whitcroft wrote:
> Seems that we are now getting strange errors mounting an ext2 root
> filesystem under 2.6.23-git18:
>
> EXT2-fs error (device sda1): ext2_check_page: bad entry in directory #2:
> rec_len is smaller than minimal - offset=0, inode=0, rec_len=0,
> name_len=0
Hmm, zero length entry in a root directory. Not nice.
> This seems to be occuring consistently since 2.6.23-git18. I have been
> back and rerun a -git17 job to confirm its not visible at that level.
> This bug is expressing itself in 2.6.23-rc1 also.
>
> I am suspicious of this commit in the -git17 -> -git18 block:
>
> commit 89910cccb8fec0c1140d33a743e72a712efd4f05
> Author: Jan Kara <jack@suse.cz>
> Date: Sun Oct 21 16:41:40 2007 -0700
>
> ext2: avoid rec_len overflow with 64KB block size
>
> /me goes debug this a bit more.
Hmm, I'd suspect that too ;) But I swear I actually tested the code ;)
So what are you using the filesystem for (or do you get the error
immediately when mounting)? How large is the filesystem?
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2007-10-24 13:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 13:15 2.6.23-git18: ext2_check_page: bad entry in directory Andy Whitcroft
2007-10-24 13:59 ` Jan Kara [this message]
2007-10-24 14:33 ` Andy Whitcroft
2007-10-24 15:03 ` Jan Kara
2007-10-24 17:07 ` Andy Whitcroft
2007-10-30 13:18 ` Jan Kara
2007-10-31 15:30 ` Jan Kara
2007-11-01 17:10 ` Andy Whitcroft
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=20071024135900.GC2652@duck.suse.cz \
--to=jack@suse.cz \
--cc=andyw@uk.ibm.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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