From: "Theodore Ts'o" <tytso@mit.edu>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: New version of the ext3 indexed-directory patch
Date: Sun, 22 Sep 2002 16:00:40 -0400 [thread overview]
Message-ID: <20020922200039.GA5709@think.thunk.org> (raw)
In-Reply-To: <3D8B557C.F9BF34D3@digeo.com>
On Fri, Sep 20, 2002 at 10:06:04AM -0700, Andrew Morton wrote:
>
> Thanks; it's good that this is moving ahead. I'll update to this
> version in the -mm patchkit, so people can test it from there
> too.
>
> What is the status of e2fsprogs support for htree? Is everything covered?
Almost. E2fsck support is fully there. With e2fsprogs 1.28, you
still need to manually set up the dir_index feature flag to convert a
filesystme to use the directory indexing feature:
debugfs -w -R "features dir_index" /dev/hdXX
debugfs -w -R "ssv def_hash_version tea" /dev/hdXX
debugfs -w -R "ssv hash_seed random" /dev/hdXX
In the 1.29 release, mke2fs will create filesystems with the directory
indexing flag set by default, and tune2fs -O dir_index will do set up
the directory indexing flag and the default hash version
automatically.
There is also a bug in e2fsprogs 1.28 so that the -D option to e2fsck
(which optimizes all directories) has a 1 in 512 chance of corrupting
a directory, due to a fenceport error that escaped my testing. This
will be fixed in 1.29, which should be released very shortly.
Folks who want to play with the latest e2fsprogs get grab it here:
bk://thunk.org:5000
- Ted
prev parent reply other threads:[~2002-09-22 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 16:41 New version of the ext3 indexed-directory patch tytso
2002-09-20 17:06 ` Andrew Morton
2002-09-22 20:00 ` Theodore Ts'o [this message]
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=20020922200039.GA5709@think.thunk.org \
--to=tytso@mit.edu \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
/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