2013-04-13 11:27:16

by Udo van den Heuvel

[permalink] [raw]
Subject: 3.8.5: incorrect semaphore state issue


This morning I did a luksOpen on an external harddisk and saw:

# cryptsetup luksOpen /dev/sde1 crypto2
Enter passphrase for /dev/sde1:
semid 557063: semop failed for cookie 0xd4dd6db: incorrect semaphore state
Failed to set a proper state for notification semaphore identified by
cookie value 223205083 (0xd4dd6db) to initialize waiting for incoming
# mount /dev/mapper/crypto2 /media

So stuff worked OK, just the unexpected messages.
I did find an ubuntu bug from 2011 so what needs fixing this time?

Please advise!

Kind regards,