[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#595732: release-notes: use 'vol_id' to get UUID, in section 4.8.1 of the notes

On Mon, Sep 06, 2010 at 10:30:12AM +0200, A Mennucc wrote:
>     To implement the UUID approach   Find out the universally unique identifier
>       of your filesystem by issuing:
>     ls -l dev/disk/by-uuid | grep hda6
>       You should get a line similar to this one:
>    lrwxrwxrwx 1 root root 24 2008-09-25 08:16 d0dfcc8a-417a-41e3-ad2e-9736317f2d8a -> ../../hda6

> This does not always work as expected: for example, for people using crypt
> filesystem, RAID or LVM, the above looks like 
>     lrwxrwxrwx 1 root root 10  6 set 08:28 0253e19c-2e69-4720-a59a-2062d82ea8fd -> ../../dm-6
> and then it is difficult to associate dm-6 to the device that is listed by 'mount' or 'df'

However, for crypt, RAID and LVM, there's no reason to convert to using
UUIDs, because these types of devices already have names that are
unambiguous and stable (at least in the case of crypt and LVM - ICBW about

> There is a much better way to find out UUID for devices: use 
>   vol_id --uuid  DEVICE
> this is more straightforward, does not need any backward guessing

That's fine, as long as we clarify at the same time that users are not
recommended to do this for devices that already have stable non-UUID

Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek@ubuntu.com                                     vorlon@debian.org

Attachment: signature.asc
Description: Digital signature

Reply to: