Systemd 207 automatically generates a mount unit for my GPT swap partition. This unit subsequently fails, because the swap partition is already mounted by fstab. Mount units based on GPT partition types should not be generated if a partition is already found in fstab. Sep 26 08:24:39 glenalbyn systemd[1]: Activating swap /dev/sda3... Sep 26 08:24:39 glenalbyn systemd[1]: Activating swap /dev/disk/by-uuid/326e9723-c2fd-4096-b15a-2ce90498da9a... Sep 26 08:24:39 glenalbyn systemd[1]: Found device ST1000DM003-1CH162. Sep 26 08:24:39 glenalbyn kernel: Adding 8388604k swap on /dev/sda3. Priority:-1 extents:1 across:8388604k FS Sep 26 08:24:39 glenalbyn systemd[1]: Activated swap /dev/sda3. --- Sep 26 08:24:39 glenalbyn swapon[268]: swapon: /dev/disk/by-uuid/326e9723-c2fd-4096-b15a-2ce90498da9a: swapon failed: Device or resource busy Sep 26 08:24:39 glenalbyn systemd[1]: dev-disk-by\x2duuid-326e9723\x2dc2fd\x2d4096\x2db15a\x2d2ce90498da9a.swap swap process exited, code=exited status=255 Sep 26 08:24:39 glenalbyn systemd[1]: Failed to activate swap /dev/disk/by-uuid/326e9723-c2fd-4096-b15a-2ce90498da9a. Sep 26 08:24:39 glenalbyn systemd[1]: Dependency failed for Swap. Sep 26 08:24:39 glenalbyn systemd[1]: Unit dev-disk-by\x2duuid-326e9723\x2dc2fd\x2d4096\x2db15a\x2d2ce90498da9a.swap entered failed state.
I have got the same problem, the difference being that my fstab uses LABEL= to designate the swap partition, instead of UUID. The outcome is the same though: systemd activates /dev/sda3 "out of nowhere" (which it didn't do before) and displays an error, while the swap space is properly mounted and enabled. There is also an error at shutdown/reboot time.
Fixed in git.
*** Bug 71848 has been marked as a duplicate of this bug. ***
(http://cgit.freedesktop.org/systemd/systemd/commit/?id=9670d58)
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.