[pkg-cryptsetup-devel] Bug#554600: Bug#554600: luksClose fails:Device (null) doesn't exist or access denied

[Jonas Meurer]

hey milan,

On 24/05/2010 Milan Broz wrote:
> On 05/23/2010 09:54 PM, ilf wrote:
> > Has anyone managed to work around this without having to reboot? 
> > Restarting /etc/init.d/cryptdisks doesn't helk.
> 
> It is quite possible that this is regression upstream
> (luksClose on underlying device which disappeared, I'll check it).

any news about that? i don't know of any cryptsetup version that
supported remove/luksClose for unplugged (and thus disappeared) devices.

still, it would be great to add such functionality (see cryptsetup issue
53 - http://code.google.com/p/cryptsetup/issues/detail?id=53).

> Anyway, you can use "dmsetup remove <device>" as temporary workaround
> if you need clean something temporarily,
> (<device> is the same like luksClose parameter)

that works indeed, just tried it. a warning message is printed though:

# dmsetup remove crypt1
Node /dev/mapper/crypt1 was not removed by udev. Falling back to direct node removal.

greetings,
 jonas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20100526/933a511e/attachment.pgp>