From: Ville Herva <v@iki.fi>
To: linux-kernel@vger.kernel.org
Subject: 2.4.35 SMP: ext3_readdir: bad entry in directory #323888: rec_len is smaller than minimal
Date: Tue, 18 Sep 2007 15:23:14 +0300 [thread overview]
Message-ID: <20070918122314.GL29062@vianova.fi> (raw)
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.
The directories in question have not been written to for ages:
>debugfs /dev/sda2
debugfs: ncheck 323888
Inode Pathname
323888 /usr/share/doc/logcheck-1.1.1
debugfs: ncheck 323882
Inode Pathname
323882 /usr/share/doc/dev86-0.15.5
debugfs: ncheck 323880
Inode Pathname
323880 /usr/share/doc/mod_put-1.3
The hardware _should_ be solid, although I can never 100% sure rule out disk
level corruption.
Does this ring any bells to anyone, short of block level corruption?
-- v --
v@iki.fi
next reply other threads:[~2007-09-18 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 12:23 Ville Herva [this message]
2007-09-18 15:12 ` 2.4.35 SMP: ext3_readdir: bad entry in directory #323888: rec_len is smaller than minimal Jan Kara
2007-09-18 16:09 ` Ville Herva
2007-09-18 16:22 ` Jan Kara
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=20070918122314.GL29062@vianova.fi \
--to=v@iki.fi \
--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