[pkg-cryptsetup-devel] Bug#585934: [udev] UUID discrepancy between cryptsetup luksUUID and udevadm info

[Guy Heatley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 16/06/2010 11:39, Milan Broz wrote:

> 
> Nope. You are mixing up two UUIDs:
> 
> luksUUID is the UUID from LUKS header of underlying device (/dev/sdc1),
> 
> ID_FS_UUID is UUID of fs on top of it (here labeled "/", it is device /dev/mapper/sdc1_crypt or so).
> 
> (You can use luksUUID even if device is not active, but FS UUID and label is visible only on active LUKS device.)
> 
> Milan

I'm not sure this is true - this device had not been opened by
cryptsetup at this point: There was no entry in /dev/mapper , it was not
an active Luks device.

- -- 
Guy


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkwYrgUACgkQtVeealbDyDVGpACeMNn6M2pe05fK30M/ComSbwwO
kDEAnjOre9MGyzdlj5ys/Lf4b7i50edf
=r49I
-----END PGP SIGNATURE-----