On Sun, 17 Dec 2017 11:49:39 -0800 Gordon Messmer wrote:
Not exactly... I'd like to know if this commit is the one that
broke the
service:
In order to determine that, someone who can reproduce the problem
needs
to revert that specific change on their system.
I did that: that do not solve the problem for me.
In my case some NFS mounts complain with either:
failed: No route to host
or
failed: Resource temporarily unavailable
but the mount finish by succeeding ~20s afterwards.
On another server the mounts failed forever.
Ex:
With that declaration in /etc/fstab:
Y:/data2 /data2 nfs rw,bg,hard,tcp,intr 0 0
no _netdev but I don't think it is worth with NetworkManager.
## ~7 seconds, similar to the time spend to see the routes below
Dec 17 21:32:51 X systemd[1]: Starting Network Manager Wait Online...
Dec 17 21:32:59 X systemd[1]: Started Network Manager Wait Online.
Dec 17 21:32:59 X systemd[1]: Mounting /data2...
Dec 17 21:33:19 X mount[996]: mount to NFS server 'Y' failed: Resource
temporarily unavailable, retrying
Dec 17 21:33:19 X systemd[1]: Mounted /data2.
with my "drop-in" routes-gw.conf those mounts are instantaneous:
Dec 17 17:32:09 X systemd[1]: Starting Network Manager Wait Online...
...
Dec 17 17:32:16 X bash[735]: Network Manager Wait Online routes took 7 seconds
Dec 17 17:32:45 X bash[735]: Network Manager Wait Online gateway took 29 seconds
Dec 17 17:32:45 X systemd[1]: Started Network Manager Wait Online.
Dec 17 17:32:45 X systemd[1]: Mounting /data2...
Dec 17 17:32:45 X systemd[1]: Mounted /data2.
I can give more details if you need.
--
francis