Re: [PATCH] Get rid of extents mount option - try 2

[Dave Kleikamp <shaggy@austin.ibm.com>]

On Sat, 2006-10-07 at 00:14 -0400, Theodore Tso wrote:
> 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.

I noticed we are missing Documentation/filesystems/ext4.txt.  Over the
weekend, I'll try to put something together with instructions on getting
the right version of e2fsprogs, etc.

> 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.

I guess this would be useful to turn the feature off immediately after
turning it on, but with the removal of the extents mount option, we no
longer have the ability to make old-style files once the feature is
turned on.  So it's unlikely that you'd be able to turn the feature off
once a file system has been used.

Also, do we update the superblock in every transaction that creates or
deletes a file?  Otherwise, how do we guarantee the count is accurate
after replaying the journal?

Shaggy
-- 
David Kleikamp
IBM Linux Technology Center