From: Hans Reiser <reiser@namesys.com>
To: Jesse Pollard <jesse@cats-chateau.net>
Cc: rmoser <mlmoser@comcast.net>,
viro@parcelfarce.linux.theplanet.co.uk,
linux-kernel@vger.kernel.org
Subject: Re: File System conversion -- ideas
Date: Mon, 30 Jun 2003 17:42:24 +0400 [thread overview]
Message-ID: <3F003E40.1040902@namesys.com> (raw)
In-Reply-To: <03063008265401.14007@tabby>
Jesse Pollard wrote:
>On Sunday 29 June 2003 14:45, rmoser wrote:
>
>
>>*********** REPLY SEPARATOR ***********
>>
>>On 6/29/2003 at 8:42 PM viro@parcelfarce.linux.theplanet.co.uk wrote:
>>
>>
>>>On Sun, Jun 29, 2003 at 08:28:47PM +0100, Jamie Lokier wrote:
>>>
>>>
>>>>Consider that many people choose ext3 rather than reiser simply
>>>>because it is easy to convert ext2 to ext3, and hard to convert ext2
>>>>to reiser (and hard to convert back if they don't like it). I have
>>>>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
>>
>>
>
>You are ASSUMING that the new filesystem requires lessthan or equal amount
>of metadata. This is NOT always true. A conversion of a full EXT2 to Riserfs
>would fail simply because there is no free space to expand the needed
>additional overhead.
>
Uh, you mean converting reiserfs to ext2 would fail.... we are more
space efficient....
>
>Going in the other direction usually is possible (again, depending on the
>filesystem) but there are exceptions... Try converting an EXT2 to DosFS.
>In place. And maintain a recoverable state when aborted.
>
>Not gonna happen.
>
>Too much depends on what the target filesystem is, and what it may require.
>
>Consider another - switching to an extent filesystem... If the datablocks
>don't move, then you need MORE extents than the current indirect pointers.
>And each extent is LARGER than the indirect pointers.
>
>Then you have to compress/condense the extents (requiring shuffling data
>blocks around to reduce the number of extents). Each requires free space
>to do it's work, and the amount of free blocks is not the same.
>
>Faster to do a copy. more reliable too. and recoverable.
>-
>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/
>
>
>
>
--
Hans
next prev parent reply other threads:[~2003-06-30 13:28 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-29 10:11 File System conversion -- ideas John Bradford
2003-06-29 13:28 ` Jamie Lokier
2003-06-29 13:50 ` David D. Hagood
2003-06-29 18:31 ` rmoser
2003-06-29 19:55 ` David D. Hagood
2003-06-29 20:05 ` rmoser
2003-06-29 20:41 ` David D. Hagood
2003-06-29 20:53 ` rmoser
2003-06-29 20:22 ` Leonard Milcin Jr.
2003-06-30 16:05 ` Henning P. Schmiedehausen
2003-06-30 16:59 ` Leonard Milcin Jr.
2003-06-30 17:04 ` Kevin Corry
2003-06-30 17:37 ` Valdis.Kletnieks
2003-07-01 9:56 ` Stewart Smith
2003-06-29 13:54 ` Leonard Milcin Jr.
2003-06-29 18:45 ` rmoser
2003-06-29 19:37 ` Leonard Milcin Jr.
2003-06-29 19:43 ` Leonard Milcin Jr.
2003-06-29 19:48 ` rmoser
2003-06-30 3:52 ` Horst von Brand
2003-07-01 10:15 ` Stewart Smith
2003-07-01 14:55 ` Leonard Milcin Jr.
2003-07-01 15:41 ` Stewart Smith
2003-07-01 16:19 ` Leonard Milcin Jr.
2003-06-29 19:44 ` rmoser
2003-06-29 19:44 ` Jamie Lokier
2003-06-29 19:46 ` rmoser
2003-06-29 20:02 ` viro
2003-06-29 20:26 ` Leonard Milcin Jr.
2003-06-29 20:31 ` rmoser
2003-07-01 10:01 ` Stewart Smith
2003-06-29 19:28 ` Jamie Lokier
2003-06-29 19:35 ` rmoser
2003-06-29 19:42 ` viro
2003-06-29 19:45 ` rmoser
2003-06-29 20:00 ` viro
2003-06-29 20:19 ` Davide Libenzi
2003-06-29 20:25 ` viro
2003-06-29 20:45 ` rmoser
2003-06-29 20:46 ` Davide Libenzi
2003-06-30 9:13 ` Nikita Danilov
2003-06-29 20:38 ` rmoser
2003-06-29 20:29 ` rmoser
2003-06-29 20:50 ` Hugo Mills
2003-06-29 21:00 ` rmoser
2003-06-29 21:10 ` Davide Libenzi
2003-06-29 21:37 ` Hugo Mills
2003-06-29 21:54 ` rmoser
2003-06-29 22:25 ` Hugo Mills
2003-06-29 20:51 ` viro
2003-06-29 21:07 ` rmoser
2003-06-29 21:08 ` Chris Friesen
2003-06-30 0:25 ` Jan Harkes
2003-06-30 0:59 ` rmoser
2003-07-01 20:03 ` Pavel Machek
2003-07-02 14:49 ` Jan Kara
2003-06-29 20:05 ` David D. Hagood
2003-06-29 20:36 ` rmoser
2003-06-30 0:05 ` Richard Braakman
2003-06-30 0:58 ` rmoser
2003-06-29 21:32 ` Diego Calleja García
2003-06-30 13:26 ` Jesse Pollard
2003-06-30 13:42 ` Hans Reiser [this message]
2003-06-30 13:56 ` Jesse Pollard
2003-07-06 19:30 ` Svein Ove Aas
2003-06-29 18:26 ` rmoser
-- strict thread matches above, loose matches on Subject: below --
2003-07-07 8:43 John Bradford
2003-07-01 16:04 Matt Reuther
2003-07-01 16:13 ` Frank Gevaerts
2003-06-30 14:11 John Bradford
2003-06-30 15:45 ` Leonard Milcin Jr.
2003-06-30 8:55 John Bradford
2003-06-30 9:36 ` Hans Reiser
2003-06-30 16:29 ` viro
2003-06-29 21:59 John Bradford
2003-06-29 20:20 John Bradford
2003-06-29 20:44 ` rmoser
2003-06-29 20:06 John Bradford
2003-06-29 18:58 John Bradford
2003-06-29 19:12 ` rmoser
2003-06-29 18:37 John Bradford
2003-06-29 18:48 ` rmoser
2003-06-29 19:42 ` Jamie Lokier
2003-06-29 16:24 John Bradford
2003-06-29 16:13 John Bradford
2003-06-29 19:16 ` Jamie Lokier
2003-06-29 6:57 rmoser
2003-06-30 13:05 ` Jesse Pollard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F003E40.1040902@namesys.com \
--to=reiser@namesys.com \
--cc=jesse@cats-chateau.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mlmoser@comcast.net \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox