[Touch-packages] [Bug 1891858] Re: Race condition in mounting /tmp at boot
*** This bug is a duplicate of bug 1891867 *** https://bugs.launchpad.net/bugs/1891867 I'm going to mark this as a dup of your other bug 1891867, but if you really think this isn't the same as that one, please feel free to comment in this bug. ** This bug has been marked a duplicate of bug 1891867 zfs not correctly imported at boot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1891858 Title: Race condition in mounting /tmp at boot Status in systemd package in Ubuntu: New Bug description: I have configured a separate /tmp partition, which is a LVM volume and create at boot via an /etc/crypttab entry vol-tmp_crypt /dev/mapper/vol-tmp /dev/urandom cipher=aes-xts-plain64,size=256,tmp,discard and mounted via an fstab entry /dev/mapper/vol-tmp_crypt /tmpext2defaults0 2 At about every third boot /tmp is not mounted and then gnome-shell cannot start, because it is not allowed to write in not mounted /tmp directory. One or two restart are required to fix this problem. ### Independent of the success of the boot process, the log message related to the problem seem to be: Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found ordering cycle on systemd-cryptsetup@vol\x2dtmp_crypt.service/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found dependency on systemd-random-seed.service/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-mount.service/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import.target/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import-cache.service/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found dependency on cryptsetup.target/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Job systemd-cryptsetup@vol\x2dtmp_crypt.service/start deleted to break ordering cyc> Aug 17 07:11:02 hostname systemd[1]: Unnecessary job for /dev/mapper/vol-tmp was removed. [...] Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found ordering cycle on systemd-random-seed.service/start Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found dependency on zfs-mount.service/start Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found dependency on zfs-import.target/start Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found dependency on zfs-import-cache.service/start Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found dependency on cryptsetup.target/start Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found dependency on systemd-cryptsetup@vol\x2dtmp_crypt.> Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Job systemd-random-seed.service/start deleted to break or> Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found ordering cycle on systemd-random-seed.service/start Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found dependency on zfs-mount.service/start Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found dependency on zfs-import.target/start Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found dependency on zfs-import-cache.service/start Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found dependency on cryptsetup.target/start Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found dependency on systemd-cryptsetup@vol\x2dtmp_crypt.> Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Job cryptsetup.target/start deleted to break ordering cyc> Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found ordering cycle on systemd-cryptsetup@vol\x2dtmp_crypt.service/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found dependency on systemd-random-seed.service/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-mount.service/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import.target/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import-cache.service/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found dependency on cryptsetup.target/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Job systemd-cryptsetup@vol\x2dtmp_crypt.service/start deleted to break ordering cyc> ### Only in a unsuccessful boot up i see: Aug 17 07:11:02
[Touch-packages] [Bug 1891858] Re: Race condition in mounting /tmp at boot
Even with around 15000 PassMark CPU Points the race to the mounting of /tmp is unreliable. I switched to a memory based /tmp. I removed the mentioned lines from /etc/crypttab and /etc/fstab and added tmpfs /tmptmpfs mode=1777,strictatime,nosuid,nodev,size=4G -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1891858 Title: Race condition in mounting /tmp at boot Status in systemd package in Ubuntu: New Bug description: I have configured a separate /tmp partition, which is a LVM volume and create at boot via an /etc/crypttab entry vol-tmp_crypt /dev/mapper/vol-tmp /dev/urandom cipher=aes-xts-plain64,size=256,tmp,discard and mounted via an fstab entry /dev/mapper/vol-tmp_crypt /tmpext2defaults0 2 At about every third boot /tmp is not mounted and then gnome-shell cannot start, because it is not allowed to write in not mounted /tmp directory. One or two restart are required to fix this problem. ### Independent of the success of the boot process, the log message related to the problem seem to be: Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found ordering cycle on systemd-cryptsetup@vol\x2dtmp_crypt.service/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found dependency on systemd-random-seed.service/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-mount.service/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import.target/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import-cache.service/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found dependency on cryptsetup.target/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Job systemd-cryptsetup@vol\x2dtmp_crypt.service/start deleted to break ordering cyc> Aug 17 07:11:02 hostname systemd[1]: Unnecessary job for /dev/mapper/vol-tmp was removed. [...] Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found ordering cycle on systemd-random-seed.service/start Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found dependency on zfs-mount.service/start Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found dependency on zfs-import.target/start Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found dependency on zfs-import-cache.service/start Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found dependency on cryptsetup.target/start Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found dependency on systemd-cryptsetup@vol\x2dtmp_crypt.> Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Job systemd-random-seed.service/start deleted to break or> Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found ordering cycle on systemd-random-seed.service/start Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found dependency on zfs-mount.service/start Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found dependency on zfs-import.target/start Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found dependency on zfs-import-cache.service/start Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found dependency on cryptsetup.target/start Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Found dependency on systemd-cryptsetup@vol\x2dtmp_crypt.> Aug 17 07:11:02 hostname systemd[1]: systemd-cryptsetup@vol\x2dtmp_crypt.service: Job cryptsetup.target/start deleted to break ordering cyc> Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found ordering cycle on systemd-cryptsetup@vol\x2dtmp_crypt.service/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found dependency on systemd-random-seed.service/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-mount.service/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import.target/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found dependency on zfs-import-cache.service/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Found dependency on cryptsetup.target/start Aug 17 07:11:02 hostname systemd[1]: cryptsetup.target: Job systemd-cryptsetup@vol\x2dtmp_crypt.service/start deleted to break ordering cyc> ### Only in a unsuccessful boot up i see: Aug 17 07:11:02 hostname systemd[1]: Reached target Block Device Preparation for
