Date: Sun, 29 Jun 2003 21:00:20 +0100
From: viro@parcelfarce.linux.theplanet.co.uk
To: rmoser <mlmoser@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: File System conversion -- ideas
Message-ID: <20030629200020.GH27348@parcelfarce.linux.theplanet.co.uk>
References: <200306291011.h5TABQXB000391@81-2-122-30.bradfords.org.uk> <20030629132807.GA25170@mail.jlokier.co.uk> <3EFEEF8F.7050607@post.pl> <20030629192847.GB26258@mail.jlokier.co.uk> <20030629194215.GG27348@parcelfarce.linux.theplanet.co.uk> <200306291545410600.02136814@smtp.comcast.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200306291545410600.02136814@smtp.comcast.net>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1905
Lines: 36

On Sun, Jun 29, 2003 at 03:45:41PM -0400, rmoser wrote:

> >> seen this written by many people who choose to use ext3.  Thus proving
> >> that there is value in in-place filesystem conversion :)
> >
> >Uh-huh.  You want to get in-kernel conversion between ext* and reiserfs?
> >With recoverable state if aborted?  Get real.
> 
> no, in-kernel conversion between everything.  You don't think it can be done?
> It's not that difficult a problem to manage data like that :D

I think that I will believe it when I see the patchset implementing it.
Provided that it will be convincing enough.  Other than that...  Not
really.  You will need code for each pair of filesystems, since
convertor will need to know *both* layouts.  No amount of handwaving
is likely to work around that.  And we have what, something between
10 and 20 local filesystems?  Have fun...

If you want your idea to be considered seriously - take reiserfs code,
take ext3 code, copy both to userland and put together a conversion
between them.  Both ways.  That, by definition, is easier than doing
it in kernel - you have the same code available and none of the limitations/
interaction with other stuff.  When you have it working, well, time to
see what extra PITA will come from making it coexist with other parts
of kernel (and with much more poor runtime environment).

AFAICS, it is _very_ hard to implement.  Even outside of the kernel.
If you can get it done - well, that might do a lot for having the
idea considered seriously.  "Might" since you need to do it in a way
that would survive transplantation into the kernel _and_ would scale
better that O((number of filesystem types)^2).
-
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/