Just checked that the same applies for encrypted non-rootfilesystems,
too. (/etc/init.d/cryptdisks*) If for example external disks are slow
crypdisk fails.
Since md and lvm devices are set up by udev: init.d/cryptdisk-early and
cryptdisks (or just cryptdisk.functions) need to contain a timeout loop
checking for their source device before failing.
Or better: If the cryptsetup can done by udev rules. (Maybe udev rules
that are created on the fly by the boot script with the help of crypttab
and a raw signature of the device?)
** Summary changed:
- crypdisk setup does not wait properly for its source devices to appear
+ crypdisk boot scripts do not wait properly for source devices to appear
** Description changed:
Binary package hint: cryptsetup
ubuntu 8.04
md and lvm devices are set up by udev rules.
cryptsetup races the hotplug system and fails if they are not set up
instantly.
cryptsetup scripts in initramfs and /etc/init.d/ should go into a
- waiting loop (0.5 sec intervals) for their devices (going on quickly
+ waiting loop (0.1 sec intervals) for their devices (going on quickly
when device is available) and timeout after a while.
while timeout not reached, do:
if my device has come up, continue
wait a 0.1 seconds
done.
if timeout has been reached ...
Lets get rid of failure, long sleep workarounds and race conditions.
Alternatively cryptsetup may be handled by udev rules, similar as md and
lvm devices are.
--
crypdisk boot scripts do not wait properly for source devices to appear
https://bugs.launchpad.net/bugs/251164
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
