Re: Tux3 Report: Initial fsck has landed

[Theodore Ts'o <tytso@mit.edu>]

On Mon, Jan 28, 2013 at 04:20:11PM -0800, Darrick J. Wong wrote:
> On Mon, Jan 28, 2013 at 03:27:38PM -0800, David Lang wrote:
> > On Mon, 28 Jan 2013, Theodore Ts'o wrote:
> > 
> > >On Sun, Jan 27, 2013 at 10:13:37PM -0800, Daniel Phillips wrote:
> > >>>The thing that jumps out at me with this is the question of how you will
> > >>>avoid the 'filesystem image in a file' disaster that reiserfs had (where
> > >>>it's fsck could mix up metadata chunks from the main filesystem with
> > >>>metadata chunks from any filesystem images that it happened to stumble
> > >>>across when scanning the disk)
> 
> Did that ever get fixed in reiserfs?

Not in resierfs, but this was something that Hans did change for
reiserfs4.

> > The situation I'm thinking of is when dealing with VMs, you make a
> > filesystem image once and clone it multiple times. Won't that end up
> > with the same UUID in the superblock?
> 
> Yes, but one ought to be able to change the UUID a la tune2fs -U.  Even
> still... so long as the VM images have a different UUID than the fs that they
> live on, it ought to be fine.

... and this is something most system administrators should be
familiar with.  For example, it's one of those things that Norton
Ghost when makes file system image copes (the equivalent of "tune2fs
-U random /dev/XXX")

					- Ted