<div dir="ltr">Disabling ifplugd didnt change the situation, and there are still missing mount points<br><br>On Tue, Feb 9, 2016 at 9:21 PM, Michael Biebl <<a href="mailto:biebl@debian.org">biebl@debian.org</a>> wrote:<br>> Am 09.02.2016 um 22:11 schrieb Sandro Tosi:<br>>>> Another idea: maybe it's related to name resolution. How is that<br>>>> configured? Does it help if you use IP adresses in /etc/fstab?<br>>><br>>> # cat /etc/resolv.conf<br>>> search OUR-DOMAIN.com<br>>> nameserver 127.0.0.1<br>>> nameserver XXX.YYY.32.33<br>>> nameserver XXX.YYY.32.22<br>>> options no_tld_query<br>>><br>>> on localhost we have unbound as dns cache with this config<br>>><br>>> # cat /etc/unbound/unbound.conf<br>>> server:<br>>> val-permissive-mode: yes<br>>> local-zone: "10.in-addr.arpa" nodefault<br>>> forward-zone:<br>>> name: .<br>>> forward-addr: XXX.YYY.32.33<br>>> forward-addr: XXX.YYY.32.22<br>>> remote-control:<br>>> control-enable: yes<br>>><br>>> the NFS storage appliance we are using is configured to have a<br>>> multiple ip addresses to resolve to the same domain name, and it<br>>> automatically balances connections between clients providing different<br>>> ip addresses, so we cannot change that.<br>><br>> For testing purposes, it should be possible to configure one client to<br>> use a fixed IP address in /etc/fstab.<br><br>oh yes, totally. I just tried that (with ifplugd still disabled) and...<span class=""></span><span class=""></span><br><br>> If the mount then doesn't fail,<br>> you have narrowed down the problem then at least.<div><br></div><div>... sadly now all the nfs shares fail to mount at first:</div><div><br></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0)">Feb 10 12:08:27 SERVER kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
</span><br>Feb 10 12:08:27 SERVER kernel: FS-Cache: Netfs 'nfs' registered for caching
<br>Feb 10 12:08:27 SERVER kernel: NFS: Registering the id_resolver key type
<br>Feb 10 12:08:27 SERVER kernel: Installing knfsd (copyright (C) 1996 <a href="mailto:okir@monad.swb.de">okir@monad.swb.de</a>).</span></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0)">Feb 10 12:08:30 SERVER kernel: igb 0000:01:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX</span><br></span><span style="font-family:monospace">Feb 10 12:08:30 SERVER mount[576]: mount to NFS server 'XXX.YYY.21.22' failed: No route to host, retrying
<br>Feb 10 12:08:30 SERVER mount[567]: mount to NFS server 'XXX.YYY.27.74' failed: No route to host, retrying
<br>Feb 10 12:08:30 SERVER mount[578]: mount to NFS server 'XXX.YYY.16.226' failed: No route to host, retrying
<br>Feb 10 12:08:30 SERVER mount[582]: mount to NFS server 'XXX.YYY.26.132' failed: No route to host, retrying
<br>Feb 10 12:08:30 SERVER mount[574]: mount to NFS server 'XXX.YYY.36.210' failed: No route to host, retrying
<br>Feb 10 12:08:30 SERVER mount[572]: mount to NFS server 'XXX.YYY.27.74' failed: No route to host, retrying
<br>Feb 10 12:08:30 SERVER mount[583]: mount to NFS server 'XXX.YYY.32.75' failed: No route to host, retrying
<br>Feb 10 12:08:30 SERVER mount[569]: mount to NFS server 'XXX.YYY.32.111' failed: No route to host, retrying
<br>Feb 10 12:08:30 SERVER mount[564]: mount to NFS server 'XXX.YYY.20.176' failed: No route to host, retrying
<br>Feb 10 12:08:30 SERVER mount[580]: mount to NFS server 'XXX.YYY.20.176' failed: No route to host, retrying
<br>Feb 10 12:08:30 SERVER mount[561]: mount.nfs: backgrounding "XXX.YYY.20.176:/VOL"
<br>Feb 10 12:08:30 SERVER mount[562]: mount.nfs: backgrounding "XXX.YYY.27.74:/VOL"
<br>Feb 10 12:08:30 SERVER mount[563]: mount.nfs: backgrounding "XXX.YYY.32.111:/VOL"
<br>Feb 10 12:08:30 SERVER mount[565]: mount.nfs: backgrounding "XXX.YYY.27.74:/VOL"
<br>Feb 10 12:08:30 SERVER mount[568]: mount.nfs: backgrounding "XXX.YYY.36.210:/VOL"
<br>Feb 10 12:08:30 SERVER mount[573]: mount.nfs: backgrounding "XXX.YYY.21.22:/VOL"
<br>Feb 10 12:08:30 SERVER mount[575]: mount.nfs: backgrounding "XXX.YYY.16.226:/VOL"
<br>Feb 10 12:08:30 SERVER mount[579]: mount.nfs: backgrounding "XXX.YYY.26.132:/VOL"
<br>Feb 10 12:08:30 SERVER mount[581]: mount.nfs: backgrounding "XXX.YYY.32.75:/VOL"
<br>Feb 10 12:08:30 SERVER mount[577]: mount.nfs: backgrounding "XXX.YYY.20.176:/VOL"
<br>Feb 10 12:08:30 SERVER nfs-common[612]: Starting NFS common utilities: statd idmapd.<br>
<br></span></div>but just above all these failures, the eth0 is marked as UP.<div><br></div><div>in the critical-chain now I no longer see the remote-fs target (so I'm not sure when it is started in relation with the networking target), is it normal?</div><div><br></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0)"># systemd-analyze critical-chain </span><br>The time after the unit is active or started is printed after the "@" character.
<br>The time the unit takes to start is printed after the "+" character.
<br>
<br>graphical.target @59.006s
<br>└─multi-user.target @59.006s
<br> └─getty.target @59.005s
<br> └─getty@tty1.service @59.005s
<br> └─<span style="font-weight:bold;color:rgb(255,84,84)">rc-local.service @5.259s +53.740s</span><span style="color:rgb(0,0,0)">
</span><br> └─basic.target @5.254s
<br> └─paths.target @5.254s
<br> └─acpid.path @5.254s
<br> └─sysinit.target @5.253s
<br> └─<span style="font-weight:bold;color:rgb(255,84,84)">nfs-common.service @1.614s +3.639s</span><span style="color:rgb(0,0,0)">
</span><br> └─rpcbind.target @1.614s
<br> └─<span style="font-weight:bold;color:rgb(255,84,84)">rpcbind.service @1.586s +27ms</span><span style="color:rgb(0,0,0)">
</span><br> └─network-online.target @1.585s
<br> └─network.target @1.585s
<br> └─<span style="font-weight:bold;color:rgb(255,84,84)">networking.service @250ms +1.335s</span><span style="color:rgb(0,0,0)">
</span><br> └─local-fs.target @249ms
<br> └─var-lib-hugetlbfs-global-pagesize\x2d2MB.mount @5.271s
<br> └─local-fs-pre.target @238ms
<br> └─<span style="font-weight:bold;color:rgb(255,84,84)">systemd-remount-fs.service @234ms +3ms</span><span style="color:rgb(0,0,0)">
</span><br> └─<span style="font-weight:bold;color:rgb(255,84,84)">keyboard-setup.service @152ms +81ms</span><span style="color:rgb(0,0,0)">
</span><br> └─<span style="font-weight:bold;color:rgb(255,84,84)">systemd-udevd.service @149ms +2ms</span><span style="color:rgb(0,0,0)">
</span><br> └─<span style="font-weight:bold;color:rgb(255,84,84)">systemd-tmpfiles-setup-dev.service @123ms +26ms</span><span style="color:rgb(0,0,0)">
</span><br> └─<span style="font-weight:bold;color:rgb(255,84,84)">kmod-static-nodes.service @113ms +6ms</span><span style="color:rgb(0,0,0)">
</span><br> └─system.slice @110ms
<br> └─-.slice @110ms<br></span><div><br>><br>> As a next step, I would remove the caching server from /etc/resolv.conf<br>> and let the system talk directly to your name server(s) which are<br>> responsible for resolving the name of the NFS server and retry with a<br>> FQDN in /etc/fstab.<br>><br>><br>> --<br>> Why is it that all of the instruments seeking intelligent life in the<br>> universe are pointed away from Earth?<br>><br><br><br><br>-- <br>Sandro "morph" Tosi<br>My website: <a href="http://sandrotosi.me/">http://sandrotosi.me/</a><br>Me at Debian: <a href="http://wiki.debian.org/SandroTosi">http://wiki.debian.org/SandroTosi</a><br>G+: <a href="https://plus.google.com/u/0/+SandroTosi">https://plus.google.com/u/0/+SandroTosi</a></div></div></div>