[dm-crypt] Help with a bug report: "Opening/creating of LUKS encrypted partitions fails with incorrect semaphore state"

[dm-crypt] Help with a bug report: "Opening/creating of LUKS encrypted partitions fails with incorrect semaphore state"

[Thomas Bächler]

[-- Attachment #1: Type: text/plain, Size: 443 bytes --]

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?


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

Re: [dm-crypt] Help with a bug report: "Opening/creating of LUKS encrypted partitions fails with incorrect semaphore state"

[Milan Broz]

On 01/24/2011 11:55 PM, Thomas Bächler wrote:
> 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?

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

Re: [dm-crypt] Help with a bug report: "Opening/creating of LUKS encrypted partitions fails with incorrect semaphore state"

[Thomas Bächler]

[-- Attachment #1: Type: text/plain, Size: 926 bytes --]

Am 25.01.2011 00:16, schrieb Milan Broz:
> On 01/24/2011 11:55 PM, Thomas Bächler wrote:
>> 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?
> 
> 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

Thank you Milan, I just received another comment:

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


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

Re: [dm-crypt] Help with a bug report: "Opening/creating of LUKS encrypted partitions fails with incorrect semaphore state"

[Milan Broz]

On 01/27/2011 05:56 PM, Thomas Bächler wrote:
> 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.

Thanks,
Milan

Re: [dm-crypt] Help with a bug report: "Opening/creating of LUKS encrypted partitions fails with incorrect semaphore state"

[Thomas Bächler]

[-- Attachment #1: Type: text/plain, Size: 778 bytes --]

Am 27.01.2011 22:42, schrieb Milan Broz:
> On 01/27/2011 05:56 PM, Thomas Bächler wrote:
>> 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.

Right now, I am forwarding messages between this list and the bug report
here: https://bugs.archlinux.org/task/22351

I cannot reproduce the problem myself.

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

I asked for that info. I also added the original reporter as a CC, maybe
that will speed things up.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]