From: rmoser <mlmoser@comcast.net>
To: Jamie Lokier <jamie@shareable.org>, linux-kernel@vger.kernel.org
Subject: Re: File System conversion -- ideas
Date: Sun, 29 Jun 2003 15:35:05 -0400 [thread overview]
Message-ID: <200306291535050230.0209B20B@smtp.comcast.net> (raw)
In-Reply-To: <20030629192847.GB26258@mail.jlokier.co.uk>
*********** REPLY SEPARATOR ***********
On 6/29/2003 at 8:28 PM Jamie Lokier wrote:
>Leonard Milcin Jr. wrote:
>> I think that filesystem conversion on-the-fly is useless. Why? If you're
>> making conversion of filesystem, you have to make good backup of data
>> from that filesystem.
>
>I disagree with this statement.
>
Me too. It's a GOOD IDEA. But... heck we don't all have tape backups.
>> It is likely that when something goes wrong during
>> conversion (power loss) filesystem will be corrupted, and data will be
>> lost.
>
>Only if the converter stores a temporarily inconsistent state on the
>filesystem. Sometimes it is possible to write a converter where the
>filesystem is in a consistent state throughout, except perhaps during
>a critical transition from one filesystem type to the other.
>
Dude come on I said put a journal in the datasystem so you DON'T get
inconsistencies like that! (A roll-back journal)
>> If you think the data is not worth to make backup - you don't have
>> to convert it. Just delete worthless filesystem, and create new one.
>> I
>> the data is worth making backup, and finally you make it - you don't
>> need to convert it.
>
>You are discounting the existence of data which is valuable enough not
>to have deleted already, yet which is not valuable enough to backup.
>I'd count local mirrors in this category: backup is too expensive, yet
>the cost of recreating the mirror is significant (days of
>downloading), therefore worth keeping if possible.
>
Mmhmm
>Also MP3 & DIVX collections etc. If you lose them it's not the end of
>the world, but you'd rather not.
>
HEY! It IS the end of the world if I lose /data/audio !!!!!!! I can't code
without music!
>> You could just delete filesystem, and restore data
>> from copy. If in turn one think the data is worth to protect it from
>> loss, but he will not do it... he risks that the data will be lost, and
>> he should not get access to such things.
> ^^^^^^
>
>It may not be worth it to _you_, but to me the cost of spare disks is
>significant enough that I choose to risk my less valuable data. It's
>my data hence my choice.
>
You forgot something. I only risk bugs in the code, that's why there's a
journal. You can have a bug in the filesystem code. You're taking the
same risks doing the conversion that you are mounting th efilesystem.
>> I think that copying data to another filesystem, and restoring it to
>> newly created is most of the time best and fastest method of converting
>> filesystems.
>
>You are right that this diminishes the value of an in-place filesystem
>converter (and defragmenter), because it is not necessary if you have
>the foresight to use multiple partitions or LVM, and enough spare disk
>space.q
>
Erm? Not everyone has spare disk space or wants to be assed with it.
Those methods take more work.
>However it would still be useful to some people, some of the time.
>
>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 :)
>
that's me. I cite that I want to go from reiser3.6 to reiser4, but I have only
one reiser3.6. I used to have all reiserfs, and yes it was a lot faster. Now
I want it back.
>-- Jamie
next prev parent reply other threads:[~2003-06-29 19:22 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-29 10:11 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 [this message]
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
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=200306291535050230.0209B20B@smtp.comcast.net \
--to=mlmoser@comcast.net \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®