Bug#618862: Bug#786393: systemd: should not try to open encrypted devs that were already opened succesfully, workaround

Am 27.08.2015 um 10:28 schrieb Martin Pitt: unmerge 756202 reopen 786393 reopen 618862 thanks Meh, #756202 is something entirely different than #786393 and #618862. Yes and no. At least the bug report in [1] has cryptswap UUID=x-xxx---xdc3 sda4_crypt

Bug#618862: Bug#786393: systemd: should not try to open encrypted devs that were already opened succesfully, workaround

unmerge 756202 reopen 786393 reopen 618862 thanks Meh, #756202 is something entirely different than #786393 and #618862. Unmerging and reopening the latter two. Sorry for the noise! Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian

Bug#786393: systemd: should not try to open encrypted devs that were already opened succesfully, workaround

Hallo, Debugging what happens on fresh installation with an encrypted / partition and a normaal /boot partition 1. The loaded initramfs image (which was generated with a the version of crypttab at the moment of generation, let's call it crypttab_initramfs), opens the entries in

Bug#786393: systemd: should not try to open encrypted devs that were already opened succesfully, workaround

Hallo, The file /etc/init/cryptdisk.conf refers to a possible race condition (/lib/cryptsetup/cryptdisks.functions) # This job currently still does not guarantee a race-free startup; instances # of cryptdisks-udev may be started in parallel with this job. hth, Wim Referencing: 3. Here