Description of problem: when running some of the cryptsetup options it complains with device-mapper: remove ioctl failed: Device or resource busy and in dmesg you get device-mapper: ioctl: unable to remove open device temporary-cryptsetup-9696 It *does* however work, but is very confusing as you would think it hadn't completed successfully. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.cryptsetup luksAddKey --key-slot 4 -q -y /dev/sde3 ~gnat/keyfile 2. 3. Actual results: [root@iridium tmp]# cryptsetup luksAddKey --key-slot 2 -q -y /dev/sde3 ~gnat/keyfile Enter any passphrase: Verify passphrase: device-mapper: remove ioctl failed: Device or resource busy Key slot 0 unlocked. device-mapper: remove ioctl failed: Device or resource busy Expected results: [root@iridium tmp]# cryptsetup luksAddKey --key-slot 2 -q -y /dev/sde3 ~gnat/keyfile Enter any passphrase: Verify passphrase: Key slot 0 unlocked. Additional info:
yes, because hald is broken... (btw it will recover, so it is not crutical but should be fixed - I provided patch for that hal bug already...) *** This bug has been marked as a duplicate of bug 613909 ***