[pkg-cryptsetup-devel] Bug#538221: [codesite-noreply at google.com: Issue 34 in cryptsetup: Command failed: device-mapper: create ioctl failed: Device or resource busy]

[Stuart Pook]

hi Milan

On 04/09/09 09:51, Milan Broz wrote:
> If there is no device with the same UUID, it is probably different problem.

there is a other device with the same UUID. It is a device that shouldn't have anything to do with one that I'm trying to mount. It is possible however that the the device I'm trying to mount was made by copying the first device. Would this cause the UUIDs to be the same?  The devices are from two different virtual machines but, if I remember correctly, one was made by copying the other (as I guess people do when cloning virtual machines).

: root; dmsetup info -c | grep CRYPT
_dev_mapper_vg0_archive        254  43 L--w    1    1      0 CRYPT-4172857b-9f99-47b7-9275-64724b91d86d                               
email_ROOT1                    254  13 L--w    1    1      0 part1-CRYPT-7c9a9e1e-715d-4c82-a88c-016a7660d2f2                         
email_var                      254  36 L--w    1    1      0 CRYPT-7b1d45da-9f14-48e4-aea3-5002279a900a                               
_dev_sda1                      254  44 L--w    1    1      0 CRYPT-6573bab9-ccf4-4b80-aa09-1dca054254c2                               
asterisk_var                   254  30 L--w    1    1      0 CRYPT-8846510f-e5ce-4e2f-82bc-bf9c772953bd                               
email_ROOT                     254  11 L--w    1    1      0 CRYPT-7c9a9e1e-715d-4c82-a88c-016a7660d2f2                               
email_data                     254  37 L--w    1    1      0 CRYPT-ac8a6724-e056-447d-8ec7-a3446ec51bb8                               
_dev_mapper_vg0_laure          254  24 L--w    1    1      0 CRYPT-416cc1cc-a0ad-4fb9-9dc8-8399ca27d5bc                               
asterisk_ROOT                  254   7 L--w    1    1      0 CRYPT-e8eb39b2-9425-4181-a5c0-687ee122704a                               
asterisk_data                  254  31 L--w    1    1      0 CRYPT-e1b12759-8c20-4b6d-973b-76a5306797fa                               
_dev_mapper_vg0_stuart         254  42 L--w    1    1      0 CRYPT-4aeb1038-d9c3-4a28-921f-462e45253767                               
var32                          254  29 L--w    1    1      0 CRYPT-431c6bf5-25e1-4904-bca2-cc0a32671ab1                               
asterisk_ROOT1                 254   9 L--w    1    1      0 part1-CRYPT-e8eb39b2-9425-4181-a5c0-687ee122704a                         

: root; cryptsetup luksDump /dev/mapper/vg0-services_var services_var | grep UUID
UUID:          	8846510f-e5ce-4e2f-82bc-bf9c772953bd
: root; cryptsetup  luksUUID  /dev/mapper/vg0-services_var
8846510f-e5ce-4e2f-82bc-bf9c772953bd
: root; cryptsetup  luksUUID  /dev/mapper/vg0-asterisk_var
8846510f-e5ce-4e2f-82bc-bf9c772953bd

I have other devices wuth the commons UUIDs so it is guess clear that I made one of the virtual machine by cloning the other.

: root; cryptsetup  luksUUID  /dev/mapper/vg0-asterisk_data
e1b12759-8c20-4b6d-973b-76a5306797fa
: root; cryptsetup  luksUUID  /dev/mapper/vg0-services_data 
e1b12759-8c20-4b6d-973b-76a5306797fa

: root; cryptsetup  luksUUID  /dev/mapper/vg0-asterisk_ROOT
e8eb39b2-9425-4181-a5c0-687ee122704a
: root; cryptsetup  luksUUID  /dev/mapper/vg0-services_ROOT
e8eb39b2-9425-4181-a5c0-687ee122704a

Do I need to change the UUID of the devices of one of the virtual machines? I must admit that I do not know who to do that.

thanks
Stuart