[systemd-devel] Mounting a new device to a mount point with an old (auto-generated) but inactive mount unit triggers an immediate unmount

Christian Rohmann christian.rohmann at frittentheke.de
Thu Jul 8 08:59:38 UTC 2021

Hey Mantas,

On 08/07/2021 10:39, Mantas Mikulėnas wrote:
>     I am then just wondering why the issue referred to
>     (https://github.com/systemd/systemd/issues/1741
>     <https://github.com/systemd/systemd/issues/1741>) is still open?
>     Are there still further plans to make systemd properly recognize
>     that the inactive unit (pointing to a mount point that is used in
>     a new and active unit) actually is superseeded and unmounting it
>     makes now sense as that hits the new, working, active mount.
> I *think* this was supposed to improve with v249:
> https://github.com/systemd/systemd/pull/19322 
> <https://github.com/systemd/systemd/pull/19322>
> https://github.com/systemd/systemd/issues/19983 
> <https://github.com/systemd/systemd/issues/19983>

nice, thanks a bunch for the pointers!

>     In any case I'd suggest then is to somehow give a warning to the
>     user as with changes to the systemd units:
>       "Warning: myfancyservice.service changed on disk. Run 'systemctl
>     daemon-reload' to reload units."
> systemd can't make non-systemd tools (such as `mount`) display warnings.

yeah, that's certainly true and it's much better to not need any 
warnings anyways .



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20210708/adac8d59/attachment-0001.htm>

More information about the systemd-devel mailing list