Help with a bug report: "Opening/creating of LUKS encrypted partitions fails with incorrect semaphore state"

I received this bug report today: https://bugs.archlinux.org/task/22351

"Opening or creating a luks encrypted partition fails with:

semid 1048580: semop failed for cookie 0xd4d3177: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223162743 (0xd4d3177) to initialize waiting for incoming notifications."

I have no idea where to start (more details inside). Any ideas?

Quoted 9 lines

I received this bug report today: https://bugs.archlinux.org/task/22351

"Opening or creating a luks encrypted partition fails with:

semid 1048580: semop failed for cookie 0xd4d3177: incorrect semaphore state Failed to set a proper state for notification semaphore identified by cookie value 223162743 (0xd4d3177) to initialize waiting for incoming notifications."

Quoted 1 line

I have no idea where to start (more details inside). Any ideas?

This is some problem in device-mapper library not in cryptsetup itself. I think we fixed that in libdevmapper but not sure now, anyway, cc-ing Peter, he will know for sure:)

Milan

Am 25.01.2011 00:16, schrieb Milan Broz:

The reportee has installed device-mapper 2.02.81. The problem occurs only with cryptsetup 1.2.0, not 1.1.3.

Quoted 4 lines

Am 25.01.2011 00:16, schrieb Milan Broz:

The reportee has installed device-mapper 2.02.81. The problem occurs only with cryptsetup 1.2.0, not 1.1.3.

strange, there should not be any change in cryptsetup related to this.

If you have some reproducer for it, please let me know.

Also please paste debug log from old (working) version to that bug so we can check if anything changed.