Hm. That function is confusing.
There are two UUIDs in fact
- on disk (applies only to LUKS)
- for activated device (aka DM-UUID)
DM-UUID is constructed from format type, on-disk UUID (if present) and
activated device name (so you are able to activate e.g. snapshot of LUKS
even with the same on-disk UUID).
crypt_get_uuid() was formerly designed to return DM-UUID but apparently I
mixed up something here (PLAIN prefix should not be visible).
so crypt_get_uuid() was supposed to return something like one of the below entries?
[ink@mtz ~]$ ls /dev/disk/by-id/dm-uuid
dm-uuid-CRYPT-LUKS1-f57ccd0520f943b9973aed73c6b67f07-zuluCrypt-500-NAAN-sdc6-781
dm-uuid-CRYPT-PLAIN-rrr
dm-uuid-CRYPT-PLAIN-zuluCrypt-500-NAAN-image-01.img-2216
dm-uuid-CRYPT-TCRYPT-zuluCrypt-500-NAAN-truecrypt-2273
dm-uuid-CRYPT-LUKS1-f57ccd0520f943b9973aed73c6b67f07-zuluCrypt-500-NAAN-sdc6-781
dm-uuid-CRYPT-PLAIN-rrr
dm-uuid-CRYPT-PLAIN-zuluCrypt-500-NAAN-image-01.img-2216
dm-uuid-CRYPT-TCRYPT-zuluCrypt-500-NAAN-truecrypt-2273
_______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
