[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
debian48 at pook.it
Fri Sep 4 07:08:37 UTC 2009
hi Jonas
On 04/09/09 00:11, Jonas Meurer wrote:
> for more information see the upstream issue at
> http://code.google.com/p/cryptsetup/issues/detail?id=34
I did so but I still have problems and this time it is not a snapshot device.
: root; cryptsetup luksOpen /dev/mapper/vg0-services_var services_var --key-file /tmp/xx
key slot 1 unlocked.
Command failed: device-mapper: create ioctl failed: Device or resource busy
I don't understand why this fails. I have never made a snapshot of this device (I rebooted last night).
: root; ls /dev/mapper/*services_var*
/dev/mapper/vg0-services_var
The machine tried to unlock a device at boot time. This failed (there is a message in my log and the virtual machine didn't start) and now I cannot luksOpen vg0-services_var.
There are no snapshots of vg0-services_var. I don't run kpartx on it (as it does not have a partition table). There is nothing in /dev/mapper which would indicate that it is already open.
I can unlock it with the magical --non-exclusive option but I don't understand why it is necessary in this case.
: root; cryptsetup luksOpen /dev/mapper/vg0-services_var services_var --key-file /tmp/xx --non-exclusive
key slot 1 unlocked.
Command successful.
: root; ls -l /dev/mapper/*services_var*
brw-rw---- 1 root disk 254, 46 2009-09-04 08:42 /dev/mapper/services_var
brw-rw---- 1 root disk 254, 23 2009-09-03 20:48 /dev/mapper/vg0-services_var
: root; cryptsetup remove services_var
: root; ls -l /dev/mapper/*services_var*
brw-rw---- 1 root disk 254, 23 2009-09-03 20:48 /dev/mapper/vg0-services_var
: root; cryptsetup luksOpen /dev/mapper/vg0-services_var services_var --key-file /tmp/xx
key slot 1 unlocked.
Command failed: device-mapper: create ioctl failed: Device or resource busy
: root; cryptsetup luksOpen /dev/mapper/vg0-services_var services_var --key-file /tmp/xx --non-exclusive
key slot 1 unlocked.
Command successful.
strange
Stuart
More information about the pkg-cryptsetup-devel
mailing list