From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin Steigerwald Subject: Re: Tux3 Report: Initial fsck has landed Date: Wed, 20 Mar 2013 11:29:41 +0100 Message-ID: <201303201129.41996.Martin@lichtvoll.de> References: <201303200000.33356.Martin@lichtvoll.de> (sfid-20130320_112832_061423_065C04E5) Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Cc: tux3@phunq.net, Daniel Phillips , Theodore Ts'o , "Darrick J. Wong" , tux3@tux3.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org To: David Lang Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tux3-bounces@phunq.net Sender: tux3-bounces@phunq.net List-Id: linux-fsdevel.vger.kernel.org Am Mittwoch, 20. M=E4rz 2013 schrieb David Lang: > On Wed, 20 Mar 2013, Martin Steigerwald wrote: > > Am Dienstag, 29. Januar 2013 schrieb Daniel Phillips: > >> On Mon, Jan 28, 2013 at 5:40 PM, Theodore Ts'o wrote: > >>> 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: > >>>>> 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") > >> = > >> Hmm, maybe I missed something but it does not seem like a good idea > >> to use the volume UID itself to generate unique-per-volume metadata > >> hashes, if users expect to be able to change it. All the metadata > >> hashes would need to be changed. > > = > > I believe that is what BTRFS is doing. > > = > > And yes, AFAIK there is no easy way to change the UUID of a BTRFS > > filesystems after it was created. > = > In a world where systems are cloned, and many VMs are started from one > master copy of a filesystem, a UUID is about as far from unique as > anything you can generate. > = > BTRFS may have this problem, but why should Tux3 copy the problem? I didn=B4t ask for copying that behavior. I just mentioned it :) -- = Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7