You are not logged in.
Recently (as in the last few days - I hadn't done an update shortly before the problem arose) my NFS mounts seem to take an age to complete - as in several minutes, sometimes hours. In fact, it takes several minutes to list my mount points on the client. By which I mean (my ~/documents contains a number of NFS mount points):
#cd documents
#ls
This now just sits there for, it seems like, forever.
It's only affecting NFS related directories. I've run through the NFS troubleshooting page on the wiki and haven't been able to fix it. The relevant bit of my fstab is as follows:
#NFS mounts
noa:/opt/backup /opt/backup nfs users,noauto,nolock,x-systemd.automount 0 0
noa:/opt/video /home/paul/documents/video nfs users,noauto,nolock,x-systemd.automount 0 0
noa:/opt/music /home/paul/documents/music nfs noauto,users,nolock,x-systemd.automount 0 0
noa:/opt/photos /home/paul/documents/photos nfs noauto,users,nolock,x-systemd.automount 0 0
noa:/opt/shared /home/paul/documents/shared nfs noauto,users,nolock,x-systemd.automount 0 0
noa:/opt/ebooks /home/paul/documents/ebooks nfs noauto,users,nolock,x-systemd.automount 0 0
I've tried replacing the server name (noa) with the ip,but it made no difference.
What else could I try?
Offline
Do you really need all of those exports?
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
I think so, yes.
Offline
Probably out of date, but it may be worth checking out this thread.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
Yes, thanks. I meant to mention that I'd already looked at that and it didn't help. Thanks anyway.
Offline
The plot thickens, it would appear that this is a client side issue as it only seems to be affecting one of my machines. All the others mount as expected.
Edit: further information, running "showmount -e noa" returns 0 exported mounts.
Edit #2: running "showmount -e 192.168.0.1" return all the mount points, but "noa" as a hostname can be correctly resolved.
Edit #3: I was mistaken in thinking that using the ip in /etc/fstab wouldn't work - it does, but why can I not get this working via hostname?
Last edited by phunni (2014-02-27 12:28:37)
Offline
Since it's only one client, I would troubleshoot h/w first: swap cable and switch port between a working client and the affected one. If that has no effect, move to s/w: are all the clients the same (distro, s/w versions)? Have you checked the logs on client and server after a mount attempt (shortly after, and after the mount finally succeeds)? To rule out any configuration issues, maybe boot the troublesome client to Arch ISO and see if the issue persists there.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
Have you checked dmesg?
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline