Re: [PATCH 0/5][64-BIT] Miscellaneous e2fsprogs 64-bit patches - description

[Theodore Tso <tytso@mit.edu>]

On Wed, Apr 15, 2009 at 02:56:15PM -0500, Eric Sandeen wrote:
> Valerie Aurora Henson wrote:
> >> Or I can forego the compression and try to save to a file: it's sparse
> >> (I only used 7GiB before it failed), but its nominal size exceeded the
> >> maximum file size limit on ext4, at which point I start getting lseek
> >> failures.
> 
> We really need some e2image format which encodes the sparseness, I think...

On my two do list for when I have copies amounts of free time is to
take the qemu image format code, and retrofit it into the I/O manager
code, and then teach e2image to use it, and then teach e2fsck,
debugfs, dumpe2fs, to be able to specify that arbitrary I/O managers
by name.  That would allow dumpe2fs, debugfs, e2fsck, etc., to operate
on an qemu-img file, where e2image would have a new option to create a
meta-data only qemu-img format file.

Now, if I only had a minion at hand to carry out my evil plans.   :-)

     	       	     	       	       	     - Ted