[dm-crypt] crypt_get_uuid does not work as expected with plain volumes

.. ink .. mhogomchungu at gmail.com
Mon Jan 21 14:40:43 CET 2013

> 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

[ink at mtz ~]$ ls /dev/disk/by-id/dm-uuid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.saout.de/pipermail/dm-crypt/attachments/20130121/4d8ff895/attachment.html>

More information about the dm-crypt mailing list