From: Valdis.Kletnieks@vt.edu
To: Andrew Morton <akpm@linux-foundation.org>,
"Duane Griffin" <duaneg@dghda.com>
Cc: linux-kernel@vger.kernel.org
Subject: 2.6.26-rc7-mmotd-0626 ext3-validate-directory-entry-data-before-use.patch
Date: Sun, 29 Jun 2008 02:25:49 -0400 [thread overview]
Message-ID: <26368.1214720749@turing-police.cc.vt.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2213 bytes --]
I'm seeing some ext3 errors, and I'm suspecting the patch
ext3-validate-directory-entry-data-before-use.patch is causing them
(since it seems to be the only thing in rc7-mmotd at the moment that
touches make_indexed_dir, and -rc5-mm3 works OK).
Jun 28 21:50:29 turing-police kernel: [ 240.784199] EXT3-fs error (device dm-7): make_indexed_dir: bad entry in directory #9894: directory entry across blocks - offset=0, inode=10144, rec_len=32, name_len=22
Jun 28 21:50:29 turing-police kernel: [ 240.784214] Aborting journal on device dm-7.
Jun 28 21:50:29 turing-police kernel: [ 240.784597] Remounting filesystem read-only
Jun 28 21:50:29 turing-police kernel: [ 240.785616] EXT3-fs error (device dm-7): do_split: bad entry in directory #9894: rec_len is smaller than minimal - offset=0, inode=2553887680, rec_len=0, name_len=0
Jun 28 21:50:29 turing-police kernel: [ 240.785616] EXT3-fs error (device dm-7) in ext3_reserve_inode_write: Journal has aborted
Jun 28 21:50:29 turing-police kernel: [ 241.027111] __journal_remove_journal_head: freeing b_committed_data
Jun 28 23:09:54 turing-police kernel: [ 5026.698415] EXT3-fs error (device dm-2): make_indexed_dir: bad entry in directory #369136: directory entry across blocks - offset=0, inode=369138, rec_len=20, name_len=11
Jun 28 23:09:54 turing-police kernel: [ 5026.698415] Aborting journal on device dm-2.
Jun 28 23:09:54 turing-police kernel: [ 5026.698519] Remounting filesystem read-only
Jun 28 23:09:54 turing-police kernel: [ 5026.702730] EXT3-fs error (device dm-2): do_split: bad entry in directory #369136: directory entry across blocks - offset=0, inode=106647, rec_len=12, name_len=1
Jun 28 23:09:54 turing-police kernel: [ 5026.702730] EXT3-fs error (device dm-2) in ext3_reserve_inode_write: Journal has aborted
I believe I have a reasonably good replicator for the error on dm-7, that's my /usr/share
and trying to 'rpm -Fvh' one specific RPM has caused it twice (in two tries).
The file systems appear to be OK (or at least the fsck.ext3 in Fedora's
e2fsprogs-1.41-0.WIP.0617.1.fc10.x86_64 says both file systems are in fact OK).
Any comments/suggestions? Any testing/debugging you'd like, or should I just revert it
and move on?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next reply other threads:[~2008-06-29 6:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-29 6:25 Valdis.Kletnieks [this message]
2008-06-29 11:31 ` Hugh Dickins
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=26368.1214720749@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=duaneg@dghda.com \
--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
all inboxes | Powered by JetHome®