From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Tue, 25 Jan 2011 00:16:15 +0100 (CET) Message-ID: <4D3E0837.6050103@redhat.com> Date: Tue, 25 Jan 2011 00:16:07 +0100 From: Milan Broz MIME-Version: 1.0 References: <4D3E0345.7030504@archlinux.org> In-Reply-To: <4D3E0345.7030504@archlinux.org> Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Subject: Re: [dm-crypt] Help with a bug report: "Opening/creating of LUKS encrypted partitions fails with incorrect semaphore state" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?ISO-8859-15?Q?Thomas_B=E4chler?= Cc: dm-crypt , Peter Rajnoha On 01/24/2011 11:55 PM, Thomas B=E4chler wrote: > I received this bug report today: https://bugs.archlinux.org/task/22351 >=20 > "Opening or creating a luks encrypted partition fails with: >=20 > semid 1048580: semop failed for cookie 0xd4d3177: incorrect semaphore sta= te > Failed to set a proper state for notification semaphore identified by > cookie value 223162743 (0xd4d3177) to initialize waiting for incoming > notifications." >=20 > 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