On Mon, Nov 17, 2008 at 03:20:04PM -0600, Eric Sandeen wrote: > > Ted, what do you think about putting make-sparse.c into e2fsprogs? > Might be handy for this sort of thing, rather than searching the > innertubes for it each time I need it ;) I've checked it into the e2fsprogs git tree, in the contrib directory. Long-term, what I'm thinking we need to do is to steal qemu's block device driver files (using a scheme similar to what I did with tdb), and create a single an I/O manager function which supports qemu qcow2 volumes. This could be used as a much more efficient way of storing raw e2image files (since it doesn't require sparse file support as well as supporting in-line zlib compression), and also as a much more efficient way of supporting "undo" functionality (by storing the original version of the file as a cow snapshot). If we were to implement it as an I/O manager, then we could even run fsck on virtual filesystems used by KVM directly from the host OS (since KVM uses qemu and therefore the qemu block device drivers as well). If some Quarumnet^H^H^H^H^H^H^H^H^H Red Hat engineers has some free time, that would be a great project for someone looking to get involved in a filesystme project. Otherwise, it's on my TODO queue, and I'll get to it one of these days.... - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
