On Sun, Jun 29, 2003 at 04:36:15PM -0400, rmoser wrote:
> Told you, I can't code it. I could work on making an initial design for the
> most important part though, the datasystem that separates the two filesystems
> and holds the meta-data and data in self-contained atoms. I KNOW I won't
> get it right the first time, but I can give you a place to start.
I don't think that's the most important part. The most important part
is figuring out a layout for the filesystem while it's in transition,
such that it is at the same time a valid ext3 filesystem (so that the
ext3 export routines can work on it) and a valid reiser4 filesystem
(so that the reiser4 import routines can work on it). And you need
to do it in such a way that the import routines won't stomp on data
that hasn't been exported yet.
If you don't have that, then there's no point in putting it in the
kernel because you won't be able to re-use the kernel fs code anyway.
Then you need to generalize this to work with any pair of filesystems.
As for the datasystem to hold the metadata: I expect you'll find that
backup/restore systems already implement this. It's what they have to
do, after all.
Richard Braakman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jun 30 2003 - 22:00:32 EST