<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - systemd-219 can't mount devices" href="https://bugs.freedesktop.org/show_bug.cgi?id=89383#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - systemd-219 can't mount devices" href="https://bugs.freedesktop.org/show_bug.cgi?id=89383">bug 89383</a> from <a class="email" href="mailto:grey@christoforo.net" title="Grey Christoforo <grey@christoforo.net>"> Grey Christoforo</a> <pre>This is a bad bug. Please see my report on the Arch Linux bug tracker on it here: <a href="https://bugs.archlinux.org/task/44658#comment134665">https://bugs.archlinux.org/task/44658#comment134665</a> This report is using systemd from Arch's [testing] repo which seems to be version 219 with some patches applied by the Arch maintainers which try to address this bug: systemd 219-6, <a href="https://www.archlinux.org/packages/testing/x86_64/systemd/">https://www.archlinux.org/packages/testing/x86_64/systemd/</a> In summary, even when the bug has been "fixed" (allowing mounts to be made again) there are cases when systemd is unmounting things it should not be when the user runs umount (seems like it unmounts ALL mounts associated with a device whenever any mount associated with that device is umounted). A bug that breaks filesystem mouting/unmounting seems particularly critical. Whatever new logic 219 introduced that created this bug should probably be reverted from the systemd release until all the mounting and unmounting corner cases can be tested and covered.</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>