[Pkg-cryptsetup-devel] Bug#444914: Bug#444914: temporary-cryptsetup-$$ files appear in /dev/mapper

[David Härdeman]

On Mon, October 1, 2007 21:16, Dick Middleton wrote:
> I have a curious effect; sometimes I get an error with luksOpen such as
> this:
>
> Failed to setup dm-crypt key mapping.
> Check kernel for support for the aes-cbc-plain cipher spec and verify that
> /dev/mapper/vg02-devil contains at least 261 sectors.
> Failed to read from key storage
> Command failed: No key available with this passphrase.
>
> None of these problems exist - it's a perfectly valid luks partition
> so the cause remains a mystery for the moment .... however:
>
> On a subsequent attempt to luksOpen it will most likely succeed but
> there then remains a file /dev/mapper/temporary-cryptsetup-$$ where $$
> is obviously a process number.  This file can be removed with a
> luksClose.

The first message is usually reported when a module is missing, but then
it is curious that it would work later.

As a test, could you do the following:

1) Before the first invocation, get a list of loaded modules
   (lsmod > modules.pre)

2) Do the two luksOpen attempts (the one that fails and the one that works)

3) Get a list of loaded modules afterwards
   (lsmod > modules.post)

4) Compare them
   (diff -u modules.pre modules.post)

5) If modules have been added, please try adding them to /etc/modules,
reboot and try luksOpen again, if it works on the first attempt, something
fishy is going on with the auto-module loading (i.e. that the libdevmapper
code is being too impatient).



-- 
David Härdeman