[pkg-cryptsetup-devel] Bug#576186: Bug#576186: cryptsetup: Setting up crypto device on Startup takes too long w/ ext3

[Milan Broz]

On 06/16/2010 09:46 PM, Jonas Meurer wrote:

>> In order to check whether using so much time is normal, I bought another
>> harddisk of the same type and mirrored my system to this new disk using
>> the "dd" command. Mounting this disk (via usb) when the system is
>> startet up already takes less then 2 seconds. 

You mean dd whole disk including LUKS or just fs?

>> Therefore i believe that some bug is causing cryptsetup to wait 50
>> seconds before doing something sensible.
> 
> i cannot imagine that this is related to the filesystem at all. dm-crypt
> doesn't mind the content of the encrypted device.

Unlocking time is calculated to take 1 second on the system where it
was formatted. Moving to another slower system will increase unlocking time,
but 50s is very long even for such situation...
(isn't it udev timeout instead?)

Can you try to unlock it manually, add debug and check whete it spend
most of time? I mean run
cryptsetup --debug luksOpen /dev/sda3 sda3_crypt

please also paste here crypsetup luksDump /dev/sda3

Anyway, if it is really problem with cryptsetup unlocking, you can fix it
by adding new passphrase (it can be the same) to new keyslot and then
kill old slot - this will recalculate iteration time leaving data intact.

Milan