Comment 19 for bug 1875577

Revision history for this message
John Gray (johngray-au) wrote : Re: [Bug 1875577] Re: Encrypted swap won't load on 20.04 with zfs root

Thanks! :)

On Sun, May 31, 2020 at 10:00 AM Richard Laager <email address hidden>
wrote:

> I have submitted this upstream:
> https://github.com/openzfs/zfs/pull/10388
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1875577
>
> Title:
> Encrypted swap won't load on 20.04 with zfs root
>
> Status in zfs-linux package in Ubuntu:
> Confirmed
>
> Bug description:
> root@eu1:/var/log# lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description: Ubuntu 20.04 LTS
> Release: 20.04
> Codename: focal
>
> root@eu1:/var/log# apt-cache policy cryptsetup
> cryptsetup:
> Installed: (none)
> Candidate: 2:2.2.2-3ubuntu2
> Version table:
> 2:2.2.2-3ubuntu2 500
> 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
>
> OTHER BACKGROUND INFO:
> ======================
>
> 1. machine has 2 drives. each drive is partitioned into 2 partitions,
> zfs and swap
>
>
> 2. Ubuntu 20.04 installed on ZFS root using debootstrap
> (debootstrap_1.0.118ubuntu1_all)
>
>
> 3. The ZFS root pool is a 2 partition mirror (the first partition of
> each disk)
>
>
> 4. /etc/crypttab is set up as follows:
>
> swap
> /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-00000_S3W6NX0M802914-part2
> /dev/urandom swap,cipher=aes-xts-plain64,size=256
> swap
> /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-00000_S3W6NX0M802933-part2
> /dev/urandom swap,cipher=aes-xts-plain64,size=256
>
>
>
> WHAT I EXPECTED
> ===============
>
> I expected machine would reboot and have encrypted swap that used two
> devices under /dev/mapper
>
>
> WHAT HAPPENED INSTEAD
> =====================
>
>
> On reboot, swap setup fails with the following messages in
> /var/log/syslog:
>
> Apr 28 17:13:01 eu1 kernel: [ 5.360793] systemd[1]:
> cryptsetup.target: Found ordering cycle on <email address hidden>
> /start
> Apr 28 17:13:01 eu1 kernel: [ 5.360795] systemd[1]:
> cryptsetup.target: Found dependency on systemd-random-seed.service/start
> Apr 28 17:13:01 eu1 kernel: [ 5.360796] systemd[1]:
> cryptsetup.target: Found dependency on zfs-mount.service/start
> Apr 28 17:13:01 eu1 kernel: [ 5.360797] systemd[1]:
> cryptsetup.target: Found dependency on zfs-load-module.service/start
> Apr 28 17:13:01 eu1 kernel: [ 5.360798] systemd[1]:
> cryptsetup.target: Found dependency on cryptsetup.target/start
> Apr 28 17:13:01 eu1 kernel: [ 5.360799] systemd[1]:
> cryptsetup.target: Job <email address hidden>/start deleted to
> break ordering cycle starting with cryptsetup.target/start
> . . . . . .
> Apr 28 17:13:01 eu1 kernel: [ 5.361082] systemd[1]: Unnecessary job
> for /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-00000_S3W6NX0M802914-part2
> was removed
>
>
> Also, /dev/mapper does not contain any swap devices:
>
> root@eu1:/var/log# ls -l /dev/mapper
> total 0
> crw------- 1 root root 10, 236 Apr 28 17:13 control
> root@eu1:/var/log#
>
>
> And top shows no swap:
>
> MiB Swap: 0.0 total, 0.0 free, 0.0 used. 63153.6 avail
> Mem
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1875577/+subscriptions
>