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 17:47:31 -0400 [thread overview]
Message-ID: <20080313214731.GE28728@mit.edu> (raw)
In-Reply-To: <alpine.DEB.1.00.0803132219590.7433@sheep.housecafe.de>
On Thu, Mar 13, 2008 at 10:22:25PM +0100, Christian Kujau wrote:
> On Thu, 13 Mar 2008, Theodore Tso wrote:
>>> 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.
>
> The md4.log is the first e2fsck run:
>
> 1) mounted fs, noticed error message in dmesg
> 2) umounted fs
> 3) ran e2fsck, right on top of this md4.log file...
>
> The 2nd run is the one after the "/dev/md4: clean" message in md4.log
Oh, right. Sorry, I missed that. I think I know what's going on.
The problem is we're not supporting long symlinks which are in extents
format. That's something which we changed, but we're going to change
back (since we need it to support filesystems with > 2**32 blocks).
I'll make e2fsprogs flexible enough to support both forms of long symlinks.
- Ted
next prev parent reply other threads:[~2008-03-13 21:47 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
2008-03-13 21:22 ` Christian Kujau
2008-03-13 21:47 ` Theodore Tso [this message]
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=20080313214731.GE28728@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 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.