Comment # 33 on bug 968727 from Franck Bui

(In reply to patrick shanahan from comment #32)
> 
> It may be "as intended", but mounts should not arbitrarily disappear.  A
> mount is a mount and because "Device Notifier" or "Disk Manager" makes that
> mount is irrelivant and should endure runlevel changes.  Expectation is the
> KEY here rather than "as intended" related to *what* app performs the mount.
> Dropping a mount w/o notice and w/o <user> direction is just plain *wrong*.
> 

My point is that systemd stops the Disk Manager service because it's not part
of the multi-user.target. And this part works as intended.

The fact that the Disk Manager chooses to umount disks it has mounted
previously because it's going to be stopped is up to this service not to
systemd.

The fact that the Disk Manager is not part of the multi-user target is also up
to the service.

So I'm going to edit the subject to reflect this and we should probably
reassign this 'issue' to the udisk2 maintainer.