All of lore.kernel.org
 help / color / mirror / Atom feed
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 17:06:53 -0600	[thread overview]
Message-ID: <4B9AC90D.6040904@redhat.com> (raw)
In-Reply-To: <20100312205435.GG32664@alea.gnuu.de>

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?

-Eric

> 04 % apt-get install
> 05 % dmesg
> 06 % dumpe2fs -x /dev/root
> 07 % e2image -r /dev/root
> 08 % e2fsck -y /dev/root
> 09 % dumpe2fs -x /dev/root
> 10 % e2image -r /dev/root
> 11 % apt-get install
> 12 % dmesg
> 
> I've put the output and images of all these commands at
> <http://alioth.debian.org/~jo-guest/ext4/>. I hope they help you somehow.
> 
> Regards, Jörg.

--
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

  reply	other threads:[~2010-03-12 23:07 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 [this message]
2010-03-13  0:03   ` Eric Sandeen
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=4B9AC90D.6040904@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.