Replying to myself: I ran an strace on cyptsetup to catch one case where it worked and one where it didn't. This is what I found: ioctl(3, DM_DEV_REMOVE, 0xdeadbeef) = -1 EBUSY (Device or resource busy) ioctl(3, DM_DEV_CREATE, 0xdeadbeef) = -1 EBUSY (Device or resource busy) In the case where it didn't work I found these failed ioctl's in the strace log. The failed DM_DEV_REMOVE also appears in case cryptsetup was successful (then I get a temporary-cryptsetup-12345 left open after cryptsetup exited). The failed DM_DEV_CREATE only appears when cryptsetup fails to open the volume. As I am no kernel hacker and unfamiliar with dm-crypt internals, it doesn't make much sense to me that a "Device or resource busy" error would occur when ioctls are sent to /dev/mapper/control. Pleae help me here. --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
