<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Enable custom path to be ignored on shutdown umount cycle"
href="https://bugs.freedesktop.org/show_bug.cgi?id=56837#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Enable custom path to be ignored on shutdown umount cycle"
href="https://bugs.freedesktop.org/show_bug.cgi?id=56837">bug 56837</a>
from <span class="vcard"><a class="email" href="mailto:aleksei.lissitsin@gmail.com" title="aleksei.lissitsin@gmail.com">aleksei.lissitsin@gmail.com</a>
</span></b>
<pre>I cannot say how it is with the up-to-date systemd. I should test on that
machine.
But back then (07.11.2012) it DID manage to unmount the host solely by
bind-mount path.
I found another workaround for that: I just manually unmount the bind-mount on
shutdown with umount (and it correctly just removes the bind-mount). Then the
host is not in mountinfo, and systemd does not try to unmount it.
(Although (this is another issue of course) for some strange reason one cannot
guarantee that on-shutdown script ends before systemd umount cycle begins, so
there is a race, but so far my script is lucky.)
So to wrap it, the problem here seems to be that
umount2(m->path, MNT_FORCE)
in function mount_points_list_umount of core/umount.c
actually manages to unmount the host (/dev/sda2) by its bind-mount name no
matter whether it is busy or not.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>