lkml.org 
[lkml]   [2003]   [Jun]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: File System conversion -- ideas
> >> Both filesystems are the full size of the partition, and so is the
> >> datasystem. The only difference is that before you start you have
> >> to make sure that the datasystem's gonna fit in with the free space
> >> on the first filesystem, and still have space to start the second
> >> filesystem, and then have space for its atoms.
> >
> >Just thought - that's going to be a problem in read-write mode :-/.
> >
> >If the disk fills up, we'd need to be able to maintain a consistant
> >filesystem structure, (at least good enough so that a separate
> >fsck-like utility could repair it - if the disk filled up, then the
> >conversion couldn't be done on-the-fly).
> >
>
>
> mmm.. hadn't thought of that.
>
> 1 second answer: Lock down some of the freespace. Do NOT let it
> get full. You know how ext2 reserves 5% for the superuser? Do that.
> Reserve enough freespace to keep working and finish the conversion.
> Predict from the beginning how much free space is going to be needed,
> and how much is going to be left over at the very final stages of the
> conversion.

That should work fine in most cases - it's not a problem to reserve
too much for the duration of the converstion, as it all gets freed
afterwards. In most cases, we'd probably only need a relatively small
amount of space to allow writes whilst the conversion is in progress.

John.
-
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/

\
 
 \ /
  Last update: 2005-03-22 13:46    [W:0.070 / U:0.068 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site