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

[David Härdeman]

On Wed, October 3, 2007 00:04, Dick Middleton wrote:
> David Härdeman wrote:
>> On Tue, Oct 02, 2007 at 10:10:40PM +0100, Dick Middleton wrote:
>>> David Härdeman wrote:
>>>> 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.
>>>
>>>> The first message is usually reported when a module is missing, but
>>>> then
>>>> it is curious that it would work later.
>>>
>>> This is the last of some 5 encrypted partitions that are opened.  The
>>> main difference is that it's on a different physical device.
>>
>> Oh, I see, then the tests I suggested are not relevant.
>> (please keep the bug report address in the CC by the way)
>
> Oops, sorry about that.
>
>> It sounds very much like this bug:
>> https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/105266
>
> It does look similar.
>
>> Could you please try running crypsetup under strace and capture a failed
>> invocation so that we can compare them?
>
> Is this helpful?
>
>   strace echo -n xxxxx| cryptsetup luksOpen /dev/mapper/vg02-devil devil

Sorry, but you need to have the strace call on the right hand side of the
pipe ("echo -n xxx | strace ..."). Could you please try again?

> Process 11295 detached
> 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.

And it didn't seem to reproduce the same error (probably because you used
a dummy password here).

-- 
David Härdeman