From: Theodore Tso <tytso@mit.edu>
To: Christian Kujau <lists@nerdbynature.de>
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsck -D segfaults in pass 3A
Date: Thu, 13 Mar 2008 16:49:49 -0400 [thread overview]
Message-ID: <20080313204949.GC28728@mit.edu> (raw)
In-Reply-To: <alpine.DEB.1.00.0803132116430.7433@sheep.housecafe.de>
On Thu, Mar 13, 2008 at 09:23:19PM +0100, Christian Kujau wrote:
> After playing around with e2fsck (today's git of the "pu" branch) a bit
> more, I still cannot use -D on this filesystem. I've tried with earlier
> version, but it still dumps core in pass 3A (Optimizing directories). I've
> compiled e2fsprogs with "CFLAGS="-g" ./configure --enable-htree; make", too
> get a few more results when this happens.
Yeah, thanks for pointing that out. Pass3A doesn't deal with
directories stored in extent format yet, and you must have one or more
directories directories in extent format. So e2fsck -D won't work.
This is a bug; I'll work on getting it fixed.
- Ted
next prev parent reply other threads:[~2008-03-13 20:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 20:23 e2fsck -D segfaults in pass 3A Christian Kujau
2008-03-13 20:49 ` Theodore Tso [this message]
2008-03-13 21:24 ` Christian Kujau
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=20080313204949.GC28728@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