I managed to grab a journal with debugging enabled. This shows that a change event for sda3 gets picked up which reactivates the dev-sda3.swap unit and then calls swapon:
Apr 20 13:11:21 ubuntu systemd[1]: dev-sda3.device: Changed dead -> plugged Apr 20 13:11:21 ubuntu systemd[1]: dev-sda3.swap: Trying to enqueue job dev-sda3.swap/start/fail Apr 20 13:11:21 ubuntu systemd[1]: dev-sda3.swap: Installed new job dev-sda3.swap/start as 2745 Apr 20 13:11:21 ubuntu systemd[1]: dev-sda3.swap: Enqueued job dev-sda3.swap/start as 2745 Apr 20 13:11:21 ubuntu systemd[1]: dev-sda3.swap: About to execute: /sbin/swapon /dev/sda3 That swapon actually fails in this log because it's busy, but it eventually succeeds. So this answers *what* is calling swapon. It does not yet answer what exactly happens in between the swapoff and mkswap calls, as doing just those from a shell don't trigger this behaviour. I suppose some uevent is generated in between which triggers the re-activation. ** Attachment added: "debug journal while this happens" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1552539/+attachment/4640717/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1552539 Title: Ubiquity Erase Disk and Install Fails to create Swap Space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1552539/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
