Bug#832566: systemd-machined breaks automounting nfs shares

[Michael Biebl]

Am 27.10.2016 um 23:13 schrieb John Pearson:
> Hello Michael,
> 
> Thanks for looking at this.
> 
> On 22/10/16 11:07, Michael Biebl wrote:
>> Am 27.07.2016 um 02:59 schrieb John Pearson:
>>> Hello Michael,
>>>
>>> After the problem first occurred I reviewed bug #767468 and purged both
>>> cgmanager and sytemd-shim, but the problem remained.  And, of course,
>>> /proc shows systemd-machined (and only systemd-machined) still "thought"
>>> /nfs/home was mounted.
>> Why is systemd-machined running? Do you have any systemd-nspawn
>> containers running where /home is symlinked or bind-mounted?
> 
> I have no idea - it was installed as part of the systemd package, and
> starts automatically at boot.  The machine runs a single KVM instance
> hosting Windows 7, managed by libvirtd.
>
>> If you stop systemd-machined, is the problem gone?
> 
> That seems to fix it without any obvious drawbacks, but I assume I'd
> have to do the same after each reboot.
> 

Is machined started by libvirtd then? What if you systemctl disable
libvirtd.service, does systemd-machined.service still start?

Can you reproduce the problem with stretch, i.e. with systemd v232?



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20170328/57e36ece/attachment.sig>