[pkg-cryptsetup-devel] Bug#586286: Bug#586286: device-mapper: ioctl: unable to remove open device temporary-cryptsetup-3433

Fri Jul 9 07:41:21 UTC 2010

On 07/08/2010 12:23 PM, Jonas Meurer wrote:
> Hey Giorgos,
>
> On 18/06/2010 Giorgos Pallas wrote:
>   
>> I am experiencing a reproducable behaviour everytime I unlock a LUKS
>> partition (unrelated with booting).
>>
>> So:
>>
>> aris:/home/encmp/gpall# cryptsetup luksOpen /dev/sdb4 dataspace_crypt
>> Enter passphrase for /dev/sdb4: 
>> device-mapper: remove ioctl failed: Device or resource busy
>>
>> At the same time something like:
>> Jun 18 09:35:40 aris kernel: [ 4210.586137] device-mapper: ioctl: unable to remove open device temporary-cryptsetup-3433
>>
>> appears at the kernel messages.
>>     
> can you provide the output of 'cryptsetup --debug luksOpen ...'?
>
>   
>> Thanks for the good job with cryptsetup!!!
>>     
> would you mind giving preliminary 2:1.1.3-1 packages a try to see
> whether that changes anything? you can find the packages at
> http://people.debian.org/~mejo/cryptsetup/
>
> greetings,
>  jonas
>   

Hello Jonas,

I'm sending you the output requested:

mordor:~/proj/cryptsetup-bug# cryptsetup --version
cryptsetup 1.1.2

mordor:~/proj/cryptsetup-bug# cryptsetup --debug luksOpen /dev/sdb2
dataspace_crypt
# cryptsetup 1.1.2 processing "cryptsetup --debug luksOpen /dev/sdb2
dataspace_crypt"
# Locking memory.
# Allocating crypt device /dev/sdb2 context.
# Trying to open and read device /dev/sdb2.
# Initialising device-mapper backend, UDEV is enabled.
# Detected dm-crypt target of version 1.7.0.
# Timeout set to 0 miliseconds.
# Password retry count set to 3.
# Iteration time set to 1000 miliseconds.
# Password verification disabled.
# Trying to load LUKS1 crypt type from device /dev/sdb2.
# Initializing crypto backend (using secure memory).
# Reading LUKS header of size 1024 from device /dev/sdb2
# Activating volume dataspace_crypt [keyslot -1] using [none] passphrase.
# dm status dataspace_crypt  OF   [16384]
Enter passphrase for /dev/sdb2:
# Trying to open key slot 0 [1].
# Trying to open key slot 1 [3].
# Reading key slot 1 area.
# DM-UUID is CRYPT-TEMP-temporary-cryptsetup-18450
# Udev cookie 0xd4dfa3d (semid 917505) created
# Udev cookie 0xd4dfa3d (semid 917505) incremented
# Udev cookie 0xd4dfa3d (semid 917505) incremented
# Udev cookie 0xd4dfa3d (semid 917505) assigned to dm_task type 0 with
flags 0xe
# dm create temporary-cryptsetup-18450
CRYPT-TEMP-temporary-cryptsetup-18450 OF   [16384]
# temporary-cryptsetup-18450: Stacking NODE_ADD (254,4) 0:6 0660
# dm reload temporary-cryptsetup-18450  OF   [16384]
# dm resume temporary-cryptsetup-18450  OF   [16384]
# temporary-cryptsetup-18450: Stacking NODE_READ_AHEAD 256 (flags=1)
# Udev cookie 0xd4dfa3d (semid 917505) decremented
# Udev cookie 0xd4dfa3d (semid 917505): Waiting for zero
# Udev cookie 0xd4dfa3d (semid 917505) destroyed
# temporary-cryptsetup-18450: read ahead is 256
# temporary-cryptsetup-18450: Setting read ahead to 256
# Udev cookie 0xd4d3f6c (semid 950273) created
# Udev cookie 0xd4d3f6c (semid 950273) incremented
# Udev cookie 0xd4d3f6c (semid 950273) incremented
# Udev cookie 0xd4d3f6c (semid 950273) assigned to dm_task type 2 with
flags 0x0
# dm remove temporary-cryptsetup-18450  OF   [16384]
device-mapper: remove ioctl failed: Device or resource busy
# Udev cookie 0xd4d3f6c (semid 950273) decremented
# Udev cookie 0xd4d3f6c (semid 950273) decremented
# Udev cookie 0xd4d3f6c (semid 950273): Waiting for zero
# Udev cookie 0xd4d3f6c (semid 950273) destroyed
# WARNING: other process locked internal device
temporary-cryptsetup-18450, retrying remove.
# WARNING: Process PID 18473 (hald-probe-volu) [PPID 1711 (hald-runner)]
spying on internal device /dev/dm-4.
# dm reload temporary-cryptsetup-18450  NF   [16384]
# Udev cookie 0xd4d58f7 (semid 983041) created
# Udev cookie 0xd4d58f7 (semid 983041) incremented
# Udev cookie 0xd4d58f7 (semid 983041) incremented
# Udev cookie 0xd4d58f7 (semid 983041) assigned to dm_task type 5 with
flags 0x0
# dm resume temporary-cryptsetup-18450  OF   [16384]
# Udev cookie 0xd4d58f7 (semid 983041) decremented
# Udev cookie 0xd4d58f7 (semid 983041): Waiting for zero
# Udev cookie 0xd4d58f7 (semid 983041) destroyed
# Udev cookie 0xd4d1219 (semid 1015809) created
# Udev cookie 0xd4d1219 (semid 1015809) incremented
# Udev cookie 0xd4d1219 (semid 1015809) incremented
# Udev cookie 0xd4d1219 (semid 1015809) assigned to dm_task type 2 with
flags 0x0
# dm remove temporary-cryptsetup-18450  OF   [16384]
# temporary-cryptsetup-18450: Stacking NODE_DEL (replaces other stacked ops)
# Udev cookie 0xd4d1219 (semid 1015809) decremented
# Udev cookie 0xd4d1219 (semid 1015809): Waiting for zero
# Udev cookie 0xd4d1219 (semid 1015809) destroyed
Key slot 1 unlocked.
# Calculated device size is 167973584 sectors (RW), offset 2056.
# DM-UUID is CRYPT-LUKS1-b63c55b1055d47fb850bb733993f555b-dataspace_crypt
# Udev cookie 0xd4d401a (semid 1048577) created
# Udev cookie 0xd4d401a (semid 1048577) incremented
# Udev cookie 0xd4d401a (semid 1048577) incremented
# Udev cookie 0xd4d401a (semid 1048577) assigned to dm_task type 0 with
flags 0x0
# dm create dataspace_crypt
CRYPT-LUKS1-b63c55b1055d47fb850bb733993f555b-dataspace_crypt OF   [16384]
# dataspace_crypt: Stacking NODE_ADD (254,4) 0:6 0660
# dm reload dataspace_crypt  OF   [16384]
# dm resume dataspace_crypt  OF   [16384]
# dataspace_crypt: Stacking NODE_READ_AHEAD 256 (flags=1)
# Udev cookie 0xd4d401a (semid 1048577) decremented
# Udev cookie 0xd4d401a (semid 1048577): Waiting for zero
# Udev cookie 0xd4d401a (semid 1048577) destroyed
# dataspace_crypt: read ahead is 256
# dataspace_crypt: Setting read ahead to 256
# Releasing crypt device /dev/sdb2 context.
# Releasing device-mapper backend.
# Unlocking memory.
Command successful.
mordor:~/proj/cryptsetup-bug# ls -la /dev/mapper/dataspace_crypt
lrwxrwxrwx 1 root root 7 Jul  9 10:36 /dev/mapper/dataspace_crypt -> ../dm-4
mordor:~/proj/cryptsetup-bug#

If you still need me to try using the packages at
http://people.debian.org/~mejo/cryptsetup/, just tell me.

By the way, I also tried to reproduce the bug using cryptsetup on a loop
device, and it could not be reproduced...

Cheers,
Giorgos