From: Eric Sandeen <sandeen@redhat.com>
To: "Jörg Sommer" <joerg@alea.gnuu.de>
Cc: "Theodore Ts'o" <tytso@mit.edu>, Andreas Dilger <adilger@sun.com>,
linux-ext4@vger.kernel.org
Subject: Re: e2fsck doesn't repair broken ext4
Date: Fri, 12 Mar 2010 18:03:57 -0600 [thread overview]
Message-ID: <4B9AD66D.1070802@redhat.com> (raw)
In-Reply-To: <4B9AC90D.6040904@redhat.com>
Eric Sandeen wrote:
> Jörg Sommer wrote:
>> Hi,
>>
>> after a system crash, I had a problem with ext4 that e2fsck didn't fix. I
>> don't know if e2fsck or ext4 was wrong. In the end, I had to remove the
>> broken directory, which succeed and solved my problem.
>>
>> These are the steps I did:
>>
>> 01 % e2fsck -fy /dev/root
>> 02 % dumpe2fsck -x /dev/root
>> 03 % e2image -r /dev/root
>
> Great, thanks for gathering the images.
>
> What version of e2fsprogs were you using?
Ok never mind on that. recent release has the same problem.
so this is 2.6.33-rc7 ...
you had:
[ 347.673207] EXT4-fs error (device hda4): make_indexed_dir: invalid rec_len for '..' in inode 425166
(wish we'd print out the actual bad rec_len there ...)
# mount -o loop 03-e2image-r mount/
# find mount/ -inum 425166
# mount/usr/share/ri/1.8/system/String
# touch mount/usr/share/ri/1.8/system/String/foobar
touch: cannot touch `mount/usr/share/ri/1.8/system/String/foobar': Input/output error
# dmesg | tail -n 1
EXT4-fs error (device loop0): make_indexed_dir: invalid rec_len for '..' in inode 425166
# debugfs 03-e2image-r
debugfs: ls -l <425166>
425166 40755 (2) 0 0 4096 11-Mar-2010 05:37 .
424052 40755 (2) 0 0 4096 1-Feb-2010 16:53 ..
0 0 (2) 0 0 0 ..
0 0 (2) 0 0 0 .
426379 100644 (1) 0 0 8494 10-Jan-2010 09:01 cdesc-String.yaml
426380 100644 (1) 0 0 293 10-Jan-2010 09:01 new-c.yaml
...
Not sure what's going on with the duplicate 0-inode entries there yet.
-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-03-13 0:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 20:54 e2fsck doesn't repair broken ext4 Jörg Sommer
2010-03-12 23:06 ` Eric Sandeen
2010-03-13 0:03 ` Eric Sandeen [this message]
2010-04-16 10:11 ` Jörg Sommer
2010-04-16 15:22 ` Eric Sandeen
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=4B9AD66D.1070802@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@sun.com \
--cc=joerg@alea.gnuu.de \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).