[dm-crypt] Cryptsetup (>= 1.7.0) luksOpen/luksClose gets stuck after open/close

Guido Trentalancia guido at trentalancia.net
Thu Apr 7 19:49:37 CEST 2016


Hello again !

On gio, 2016-04-07 at 18:23 +0200, Milan Broz wrote:
> 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).

I have checked again and it does not depend on a missing udev rule or
on LVM. It is a bug in cryptsetup version >= 1.7.0.

Any idea on how to fix it ?

Regards,

Guido


More information about the dm-crypt mailing list