On Tue, Jul 01, 2003 at 04:55:58PM +0200, Leonard Milcin Jr. wrote:
> I think of some sort of overlay filesystem on top of that *thing*. In
> this case ovarlay filesystem could serve as redo log in database system.
> Then we need only worry with read operations, not write. Writes will be
> stored in redo log, and eventually they will be included when actual
> read only filesystem will be converted.
This is exactly what has been said before in this thread
- i.e. mount the new FS over the old one (union style)
and new writes go to the new FS.
I really thing LVM resizing automagick would be the way to go to.
*much* cleaner and easier to implement.
The real useful thing to do would be to write a utility that would
convert non-LVM systems to LVM.
-- Stewart Smith Vice President, Linux Australia http://www.linux.org.au (personal: http://www.flamingspork.com) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.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 Jul 07 2003 - 22:00:13 EST