[systemd-bugs] [Bug 86930] systemd tries to swapon devices which have already been swapon'd

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=86930

--- Comment #2 from Benjamin Xiao <ben.r.xiao at gmail.com> ---
I can confirm this on Debian testing with systemd 215-7

Seems like systemd-fstab-generator and systemd-gpt-auto-generator are competing
with each other.

In the freedesktop documentation, it says that systemd should run the fstab
generated unit file first before using the gpt auto generated unit file.
However, it seems like they're running at the same time, resulting in a race
condition. Sometimes swap is mounted via the fstab entry and other times it's
mounted via the gpt-auto-generator.

This isn't a problem for people who don't mess around with the fstab entry and
leave it as default. But for people who have SSD drives and enable the discard
option for their swap partition via fstab, this becomes problematic since it
isn't guaranteed that fstab will run first and apply the discard. Indeed
sometimes my swap gets automounted and the fstab mount will fail with "Device
or resource busy".

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20141205/4163b991/attachment.html>