From: "Thomas Bächler" <thomas@archlinux.org>
To: Milan Broz <mbroz@redhat.com>
Cc: dm-crypt <dm-crypt@saout.de>, Peter Rajnoha <prajnoha@redhat.com>
Subject: Re: [dm-crypt] Help with a bug report: "Opening/creating of LUKS encrypted partitions fails with incorrect semaphore state"
Date: Thu, 27 Jan 2011 17:56:27 +0100 [thread overview]
Message-ID: <4D41A3BB.5080407@archlinux.org> (raw)
In-Reply-To: <4D3E0837.6050103@redhat.com>
[-- 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 --]
next prev parent reply other threads:[~2011-01-27 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 22:55 [dm-crypt] Help with a bug report: "Opening/creating of LUKS encrypted partitions fails with incorrect semaphore state" Thomas Bächler
2011-01-24 23:16 ` Milan Broz
2011-01-27 16:56 ` Thomas Bächler [this message]
2011-01-27 21:42 ` Milan Broz
2011-01-28 8:23 ` Thomas Bächler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D41A3BB.5080407@archlinux.org \
--to=thomas@archlinux.org \
--cc=dm-crypt@saout.de \
--cc=mbroz@redhat.com \
--cc=prajnoha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.