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

[Markus Melms]

Hi Milan,

> >> 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?

I mean the whole disk (/dev/sda).

> 
> >> 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?)

Any hints how I could check this?

> 
> 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

I need the crypto partition in order to boot up the system. I would
need a copy in order to try it manually. But then the error would not
occur. Mounting this disk (via usb) when
the system is startet up already takes less then 2 seconds. 

> 
> please also paste here crypsetup luksDump /dev/sda3

Result:

root at playstation:# cryptsetup luksDump /dev/sda3
Aufruf fehlgeschlagen: /dev/sda3 is not a LUKS partition 
# "Aufruf fehlgeschlagen" means sth. like "Command failed"

root at playstation:# cat /etc/crypttab 
# <target name>	<source device>		<key file>
# <options>
cryptofs	/dev/sda3		none
check,tries=3,cipher=aes-cbc-essiv:sha256,loud

Does this help?

Best regards,
Markus