From: Theodore Tso <tytso@mit.edu>
To: Dave Kleikamp <shaggy@austin.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] Get rid of extents mount option - try 2
Date: Sat, 7 Oct 2006 00:14:39 -0400 [thread overview]
Message-ID: <20061007041439.GA5478@thunk.org> (raw)
In-Reply-To: <1160176800.8658.70.camel@kleikamp.austin.ibm.com>
On Fri, Oct 06, 2006 at 06:20:00PM -0500, Dave Kleikamp wrote:
> To be honest, I've been lazy and I haven't even tried to get the new
> e2fsprogs. I just grabbed the latest from the mercurial repository,
> http://e2fsprogs.sourceforge.net/e2fsprogs-hacking.html , and it doesn't
> work for me either. Ted?
>
> Hold off on the patch until we figure it out. :-)
I've been busy cleaning up the userspace extents patches before I'm
willing to accept them into the mainline e2fsprogs tree. So it's not
yet in Mercurial yet. It's coming soon; but in the meantime, my
interim patchset which I've been using to hack on the extents patches
plus signed-char-powerpc-dirhash problem can be found at:
ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/e2fsprogs-interim
Both a rolled-up patch file plus a broken-out tar.gz file are
available there. The current version on the above URL is
e2fsprogs-1.39-tyt1. Note that you will have to take the
f_extents/image.gz from the broken-out tar file and copy it into
tests/f_extents/image.gz or the f_extents regression test will fail.
In addition, the f_lotsbad test regression test is also known to fail
in 1.39-tyt1, and that regression test failure can be safely ignored
for now.
This should be good enough for the extents patches that Shaggy has
been queuing up.
- Ted
P.S. Before we add the extents patch, I just thought of one
additional change that might be good to add. Could we add an u32
field in the superblock which counts the number of files with extents,
and is automatically incremented and decremented as necessary by the
kernel, and which can be checked by e2fsck? It would be really useful
for making it easy for tune2fs to be able to tell if it can safely
remove the extents feature from the filesystem, or whether it should
refuse such a request.
next prev parent reply other threads:[~2006-10-07 4:14 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 18:23 Updated ext4/jbd2 patches based on 2.6.19-rc1 Dave Kleikamp
2006-10-05 20:19 ` Andrew Morton
2006-10-05 23:25 ` Linus Torvalds
2006-10-06 12:50 ` Dave Kleikamp
2006-10-06 16:11 ` Linus Torvalds
2006-10-05 21:59 ` Andrew Morton
2006-10-06 0:39 ` Andrew Morton
2006-10-10 6:29 ` Andrew Morton
2006-10-10 7:54 ` Suparna Bhattacharya
2006-10-10 8:14 ` Andrew Morton
2006-10-10 20:02 ` [RFC] [PATCH] Documentation/filesystems/ext4.txt Dave Kleikamp
2006-10-10 20:56 ` Andrew Morton
2006-10-11 17:03 ` Andreas Dilger
2006-10-12 14:18 ` Valerie Clement
2006-10-06 3:55 ` Updated ext4/jbd2 patches based on 2.6.19-rc1 Andrew Morton
2006-10-06 3:58 ` Andrew Morton
2006-10-06 10:34 ` Alex Tomas
2006-10-06 4:54 ` Randy Dunlap
2006-10-06 5:05 ` Andrew Morton
2006-10-06 5:53 ` Andreas Dilger
2006-10-06 6:04 ` Andrew Morton
2006-10-06 6:41 ` Andreas Dilger
2006-10-06 6:50 ` Andrew Morton
2006-10-06 10:31 ` Alex Tomas
2006-10-06 13:57 ` Andrew Morton
2006-10-07 20:09 ` alex
2006-10-06 6:52 ` Suparna Bhattacharya
2006-10-06 12:21 ` Theodore Tso
2006-10-06 21:10 ` [PATCH] Get rid of extents mount option Dave Kleikamp
2006-10-06 21:21 ` [PATCH] Get rid of extents mount option - try 2 Dave Kleikamp
2006-10-06 22:32 ` Andrew Morton
2006-10-06 23:20 ` Dave Kleikamp
2006-10-07 4:14 ` Theodore Tso [this message]
2006-10-07 15:53 ` Dave Kleikamp
2006-10-07 17:20 ` Theodore Tso
2006-10-07 19:45 ` Alex Tomas
2006-10-07 19:57 ` Andrew Morton
2006-10-10 18:48 ` Dave Kleikamp
2006-10-10 21:07 ` Theodore Tso
2006-10-10 21:18 ` Andrew Morton
2006-10-11 17:16 ` Andreas Dilger
2006-10-06 4:31 ` Updated ext4/jbd2 patches based on 2.6.19-rc1 Andrew Morton
2006-10-06 5:58 ` Andreas Dilger
2006-10-06 6:10 ` Andrew Morton
2006-10-06 6:48 ` Andreas Dilger
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=20061007041439.GA5478@thunk.org \
--to=tytso@mit.edu \
--cc=akpm@osdl.org \
--cc=linux-ext4@vger.kernel.org \
--cc=shaggy@austin.ibm.com \
/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