Proposal/RFC: new metadata-specific UUID for V5 supers

[Carlos E. R.]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2015-04-28 03:20, Dave Chinner wrote:

>> Well, it's just the loss of ability to change UUID, which is
>> something People Used To Do(tm), and now can't.  It does come up.
>> Honestly if it had been done from day 0, it'd be a no-brainer I
>> think.  Doing it now, with an incompat flag, might not be a
>> reasonable tradeoff.
> 
> I think that labels are a far better way of dealing with this 
> problem. Get rid of the UUID mount checking (and hence the nouuid 
> mount option), and tell people to use by-label instead of by-uuid
> to identify their filesystems when doing clones and snapshots.
> Labels make it much easier for humans to identify the filesystem
> than UUIDs...

As a plain user, I can say that I have needed to mount both the
filesystem and its backup image, but Linux refused on the basis of the
id being the same. Of course, all identifiers are the same, label and
uuid.

- -- 
Cheers / Saludos,

		Carlos E. R.

  (from 13.1 x86_64 "Bottle" (Minas Tirith))
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iF4EAREIAAYFAlU+4/oACgkQja8UbcUWM1wazAD9GYaGlF722BiADT5xt1UCvHOj
f72zxyn7Ti4Xoxho6vAA/2Lik11x1rCy9vEdt6OYo8Z7yYvDncLHKfx+yvt9UxsU
=VNrO
-----END PGP SIGNATURE-----