From: Jan Kara <jack@suse.cz>
To: Ville Herva <v@iki.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.35 SMP: ext3_readdir: bad entry in directory #323888: rec_len is smaller than minimal
Date: Tue, 18 Sep 2007 18:22:56 +0200 [thread overview]
Message-ID: <20070918162256.GA3280@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20070918160949.GR29062@vianova.fi>
> On Tue, Sep 18, 2007 at 05:12:06PM +0200, you [Jan Kara] wrote:
> > Hello,
> >
> > > I got a bunch of these into dmesg:
> > >
> > > EXT3-fs error (device sd(8,2)): ext3_readdir: bad entry in directory #323880: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
> > > EXT3-fs error (device sd(8,2)): ext3_readdir: bad entry in directory #323888: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
> > > EXT3-fs error (device sd(8,2)): ext3_readdir: bad entry in directory #323882: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
> > >
> > > The kernel is 2.4.35 SMP, dual-processor. The scsi driver is Fusion MPT SCSI
> > > Host driver 2.05.16.
> > >
> > > The device is /dev/sda2, root fs.
> > >
> > > One line per each directory had dropped into dmesg each night (I think
> > > during updatedb) before I noticed.
> > Interesting. Can you look (using debugfs) on the content of the
> > /usr/share/doc/ directory? It seems like parts of it have been zeroed
> > out...
>
> Unfortunately, no. I removed those directories because those were the only
> ones causing problems and wasn't able to reboot for a proper fsck
> immediately. The rm -rf command gave no errors (to stdout or dmesg), and a
> read-only fsck right after that gave no errors on the directory structure.
>
> Sorry for the sparse details, but when you have these kind of problems on
> live servers, you tend to forget the debuggability...
Yes, I can understand that :). It's just that now it's hard to find
out what has really happened. Anyway, thanks for your report.
Honza
--
Jan Kara <jack@suse.cz>
SuSE CR Labs
next prev parent reply other threads:[~2007-09-18 16:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 12:23 Ville Herva
2007-09-18 15:12 ` Jan Kara
2007-09-18 16:09 ` Ville Herva
2007-09-18 16:22 ` Jan Kara [this message]
2007-09-18 16:33 ` Ville Herva
2007-09-18 21:47 ` Willy Tarreau
2007-09-20 12:45 ` Ville Herva
2007-09-20 13:20 ` Willy Tarreau
2007-09-20 13:25 ` Ville Herva
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=20070918162256.GA3280@atrey.karlin.mff.cuni.cz \
--to=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=v@iki.fi \
/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
all inboxes | Powered by JetHome®