From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@archlinux.org>
Received: from archlinux.org (gerolde.archlinux.org [66.211.214.132])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Thu, 27 Jan 2011 17:56:32 +0100 (CET)
Message-ID: <4D41A3BB.5080407@archlinux.org>
Date: Thu, 27 Jan 2011 17:56:27 +0100
From: =?ISO-8859-15?Q?Thomas_B=E4chler?= <thomas@archlinux.org>
MIME-Version: 1.0
References: <4D3E0345.7030504@archlinux.org> <4D3E0837.6050103@redhat.com>
In-Reply-To: <4D3E0837.6050103@redhat.com>
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature";
 boundary="------------enigDB83B8E186E6756E8E109E7C"
Subject: Re: [dm-crypt] Help with a bug report: "Opening/creating of LUKS
 encrypted partitions fails with incorrect semaphore state"
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: Milan Broz <mbroz@redhat.com>
Cc: dm-crypt <dm-crypt@saout.de>, Peter Rajnoha <prajnoha@redhat.com>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigDB83B8E186E6756E8E109E7C
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable

Am 25.01.2011 00:16, schrieb Milan Broz:
> On 01/24/2011 11:55 PM, Thomas B=E4chler wrote:
>> I received this bug report today: https://bugs.archlinux.org/task/2235=
1
>>
>> "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?
>=20
> 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:)
>=20
> 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.


--------------enigDB83B8E186E6756E8E109E7C
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEAREIAAYFAk1Bo7sACgkQEda5KzHP/VDOJgCggC30IT+g5SQWV2Y2lUfpK/a5
dNIAniL1fN7pvG8cjw6oUJGz60JlDADk
=3Z1s
-----END PGP SIGNATURE-----

--------------enigDB83B8E186E6756E8E109E7C--