From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <htd@fancy-poultry.org>
Received: from moutng.kundenserver.de (moutng.kundenserver.de
	[212.227.126.186]) by mail.saout.de (Postfix) with ESMTP
	for <dm-crypt@saout.de>; Sat, 29 Aug 2009 18:40:15 +0200 (CEST)
Received: from liesel.fancy-poultry.org (localhost [127.0.0.1])
	by liesel.fancy-poultry.org (Postfix) with ESMTP id 59EC5182025AD
	for <dm-crypt@saout.de>; Sat, 29 Aug 2009 18:45:00 +0200 (CEST)
Date: Sat, 29 Aug 2009 18:45:00 +0200
Message-ID: <87zl9ibmcz.wl%htd@fancy-poultry.org>
From: Heinz Diehl <htd@fancy-poultry.org>
In-Reply-To: <f70f2e870908290846o3007aa21i80caec4ed31cc8d9@mail.gmail.com>
References: <f70f2e870908271439s5d0dd22er3c72c4d3de515813@mail.gmail.com>
	<4A97DF3D.6010504@redhat.com>
	<f70f2e870908290846t18149b70g26c8466c98349dff@mail.gmail.com>
	<f70f2e870908290846o3007aa21i80caec4ed31cc8d9@mail.gmail.com>
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Subject: Re: [dm-crypt] Command failed: Can not access device on luksOpen
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: dm-crypt@saout.de

At Sat, 29 Aug 2009 16:46:33 +0100,
Paul Bradley wrote:

> Since the device shouldn't be open by anything (I've even rebooted the box to ensure no stale locks) how do I go about
> finding out what has it locked, and how do I safely remove that lock?

Have you checked /dev/mapper/ for the devicename?