<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - systemd tries to swapon devices which have already been swapon'd" href="https://bugs.freedesktop.org/show_bug.cgi?id=86930#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - systemd tries to swapon devices which have already been swapon'd" href="https://bugs.freedesktop.org/show_bug.cgi?id=86930">bug 86930</a> from <a class="email" href="mailto:ben.r.xiao@gmail.com" title="Benjamin Xiao <ben.r.xiao@gmail.com>"> Benjamin Xiao</a> <pre>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".</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>