I am not sure if anyone from Ubuntu will even respond here, but I
checked upstream code and provided logs (btw thanks for them, very
usefull here).

What happens here is:
- system is fully udev managed, both userspace and kernel are recent enough
- according to logs, something during "udev event" acknowledge fails and 
libdevmapper takes old compatible path
(trying to create/remove link in /dev/ itself) and also decrementing cookie 
semaphore.
- unfortunately, the event _was_ triggerred and dmsetup udevcomplete called and 
because both udev and libdevmapper decrements the semaphore, the second call 
fails with the message above.

I think the reason is in kernel (kernel do not annonce for some that
uvent was sent) but I was not able to reproduce this.  If you have some
way how to reproduce it reliably, please let me know...

(The bug is not critical, the operation itself finishes correctly.)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719388

Title:
  semop failed for cookie 0xd4d09ef: incorrect semaphore state during
  luksOpen

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to