FS#23911 - [nfs] mounting NFSv4 fails on very fast systems
Attached to Project:
Arch Linux
Opened by Andreas Radke (AndyRTR) - Sunday, 24 April 2011, 10:28 GMT
Last edited by Tom Gundersen (tomegun) - Wednesday, 18 May 2011, 15:38 GMT
Opened by Andreas Radke (AndyRTR) - Sunday, 24 April 2011, 10:28 GMT
Last edited by Tom Gundersen (tomegun) - Wednesday, 18 May 2011, 15:38 GMT
|
Details
Description: Mounting a NFSv4 share the "netfs" hook fails
to mount it giving a "no route to host". This only happens
on my fastest SandyBridge Quad core system with a SSD as
boot drive. All other clients can mount it well. See also
https://bbs.archlinux.org/viewtopic.php?id=113497. Not sure if this is related to the NFS packages or because our initscripts give a return to fast before the connection is really online. Maybe there's somewhere a "&" after a call that shouldn't be there. Therefor I also assign it to our initscript maintainer. I have to add "mount /mnt/nfs" to my rc.local that most times works at that late state. Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: |
This task depends upon
Closed by Tom Gundersen (tomegun)
Wednesday, 18 May 2011, 15:38 GMT
Reason for closing: Fixed
Additional comments about closing: Probably fixed by udev-168-2. Please reopen if that's not the case.
Wednesday, 18 May 2011, 15:38 GMT
Reason for closing: Fixed
Additional comments about closing: Probably fixed by udev-168-2. Please reopen if that's not the case.
What is your fstab entry?
I think one solution might be to make netcfg not fork until it has set up all connections (and dhcp has finished setting up). I thoght nfs should keep trying to connect even if there is not connection at first try though...
192.168.0.90:/ /mnt/nfs nfs4 user 0 0
On my desktop where this fails to mount I don't use netcfg but plain rc.conf static IP adress configuration. Notebook that can mount it use netcfg and wlan.
You are right, we probably need to wait for dhcp to finish.
However, I should point out that just because we have an IP doesn't mean you can access your server (in your case it probably does), so this is not a satisfactory solution. Have you tried giving some options to nfs in fstab to make it retry mounting until it succeeds? I'm not sure but I thought this should be possible.
- I don't know any option you mean. But I use "nofail" in my notebooks fstab.
Could you post your rc.conf?