On 20/06/2021 06:58, Ed Greshko wrote:
On 19/06/2021 19:22, Patrick O'Callaghan wrote:
On Sat, 2021-06-19 at 11:58 +0800, Ed Greshko wrote:
I removed the WantedBy=multi-user.target from the mount unit. I then
did a daemon-reload.
I noted that there were 2 broken syslinks associated with the mounts
in
/etc/systemd/system/multi-user.target.wants so I deleted them. I
then rebooted.
AFAIK anything in the [Install] section is only processed statically by
the 'enable' and 'disable' actions, i.e. not at runtime. That being the
case, I don't see how the unit is ever going to be activated, but I
admit that my understanding of all this is hazy at best.
Well, all I know at the moment is the VM's work, the bare metal system doesn't.
The other weird thing I can't explain is that I see the follwing line in the journal at the boot time
before any user logs in.
Jun 20 06:42:16 meimei.greshko.com systemd[1]: aux.automount: Got automount request for /aux, triggered by 2344 (daemon-init)
Jun 20 06:42:16 meimei.greshko.com systemd[1]: Mounting nfs mount aux...
I think this will remain an unsolved mystery.
OK. My mystery has been "solved" by observation/deduction and a log entry.
Took my blinders off, and noticed the following in the journal at boot time.
Jun 20 06:42:16 meimei.greshko.com dnsmasq[2449]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
Jun 20 06:42:16 meimei.greshko.com dnsmasq-dhcp[2449]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Jun 20 06:42:16 meimei.greshko.com systemd[1]: aux.automount: Got automount request for /aux, triggered by 2344 (daemon-init)
Jun 20 06:42:16 meimei.greshko.com systemd[1]: Mounting nfs mount aux...
But I failed to look a bit further into the log to see.
Jun 20 06:42:19 meimei.greshko.com libvirtd[2306]: hostname: meimei.greshko.com
Jun 20 06:42:19 meimei.greshko.com libvirtd[2306]: cannot open directory '/aux/linux-releases/bsd': No such file or directory
Jun 20 06:42:19 meimei.greshko.com libvirtd[2306]: internal error: Failed to autostart storage pool 'bsd': cannot open directory '/aux/linux-releases/bsd': No such file or directory
I then departed from my normal routine. When I login after boot all of the NFS mounts are active. So, this time
I waited for them to auto-unmount. I then started virt-manager. And, what do you know, the NFS mounts all became
active again.
So, I've concluded that my NFS mounting issues are all related to running virtualization stuff.
--
Remind me to ignore comments which aren't germane to the thread.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
