On 04/07/2016 04:26 PM, Guido Trentalancia wrote: > Hello. > > Cryptsetup version 1.7.0 and 1.7.1 gets stuck on luksOpen and luksClose > immediately after the device has been opened or closed. If it is stuck on semop operation, then it is problem of underlying device-mapper library (that uses system semaphores for synchronization). Usually it is caused by a misconfiguration of udev rules (there must be udev rule calling dmsetup udevcomplete otherwise it ends like in your case). Please check that you have these udev rules installed - they are usually part of lvm2/dsmetup subpackage (depends on distro, for example in Debian it is /lib/udev/rules.d/55-dm.rules). ... > > The device is closed correctly, however the cryptsetup process has to > be killed again to get the shell prompt back. Does calling "dmsetup udevcomplete_all" help? If so, see above. > Previous versions (such as 1.6.8 and earlier ones) are not affected by > this bug. I guess 1.6.8 is either compiled without udev support or you reinstalled something. (cryptsetup 1.7.0 does not contain any related changes to this problem). Please better post cryptsetup command with --debug, strace only on request (it does not contain important information, moreove ot can contain your password). Also always mention your distro and version. Thanks, Milan _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
