From: Theodore Tso <tytso@mit.edu>
To: Christian Kujau <lists@nerdbynature.de>
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsck not fixing all corruptions on the first run?
Date: Thu, 13 Mar 2008 16:54:26 -0400 [thread overview]
Message-ID: <20080313205426.GD28728@mit.edu> (raw)
In-Reply-To: <alpine.DEB.1.00.0803131923420.7433@sheep.housecafe.de>
On Thu, Mar 13, 2008 at 07:34:40PM +0100, Christian Kujau wrote:
> e2fsck indeed does find a few corruptions, fixes them. The next run, e2fsck
> says "clean" of course. But when I ran with -f, e2fsck did find more
> (small) corruptions, see the full log here:
>
> http://nerdbynature.de/bits/e2fsprogs.pu/md4.log
> http://nerdbynature.de/bits/e2fsprogs.pu/
Hmm. What I really need is *first* e2fsck run, to see what it did.
> Q: How comes e2fsck would skip a few things during the first run? If it
> (technically) has to, couldn't it NOT mark the fs clean so that one
> knows it has to run fsck again?
It's supposed to fix everything in one run. If it doesn't, it's a
bug. It usually means that either it attempted to fix a corruption,
and didn't fix it correctly, or some corruption confused it enough
that it didn't spot another corruption in the same run.
But as a result, that's why it's most useful to know what it found and
fixed in the first e2fsck run. Seeing both e2fsck logs is most useful
when trying to determine why it wasn't able to fix everything in one
go.
- Ted
next prev parent reply other threads:[~2008-03-13 20:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 18:34 e2fsck not fixing all corruptions on the first run? Christian Kujau
2008-03-13 20:54 ` Theodore Tso [this message]
2008-03-13 21:22 ` Christian Kujau
2008-03-13 21:47 ` Theodore Tso
2008-03-13 21:59 ` Christian Kujau
2008-03-13 22:16 ` Theodore Tso
2008-03-14 7:17 ` Christian Kujau
2008-03-14 3:20 ` [PATCH, E2FSPROGS] e2fsck: Support long symlinks which use extents Theodore Ts'o
2008-03-14 3:20 ` [PATCH, E2FSPROGS] e2fsck: Check for fast symlinks that have EXTENTS_FL set Theodore Ts'o
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=20080313205426.GD28728@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=lists@nerdbynature.de \
/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).