The workaround proposed here will not work in the archive at large. I
believe the correct fix is to signal mountall to rescan at the end of
the do_swap() and do_tmp() functions in
/lib/cryptsetup/cryptdisks.functions. Could someone test whether this
fixes the issue?:
PID=$(status mountall 2>/dev/null | sed -e '/,/{s/.*,[^0-9]*//;q};d')
[ -n "$PID" ] && kill -USR1 $PID || true
If it doesn't, please also add the following command to the top of the
"script" block in /etc/init/cryptdisks-enable.conf:
initctl log-priority debug
and attach the resulting /var/log/syslog file to this bug.
** Changed in: cryptsetup (Ubuntu)
Importance: Undecided => High
** Summary changed:
- /dev/mapper/tmp encrypted with /dev/urandom not mounted on bootup
+ race condition between encrypted device creation and mountall probing with
random-encrypted devices (swap, tmp)
--
race condition between encrypted device creation and mountall probing with
random-encrypted devices (swap, tmp)
https://bugs.launchpad.net/bugs/475936
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
