I have a small home network running, with a NAS box (ICY BOX IB-NAS5220) exporting
/home for my various Linux Mint machines.
/etc/exports on the NAS:
The relevant line of
/etc/fstab on the clients:
192.168.178.3:/mnt/md1/public /home nfs nolock,nfsvers=3 0 0
nolock is necessary to get Firefox to cooperate.
nfsvers=3 is a limitation of the NAS. Paths and IPs are tripple-checked OK.)
However, I experience rather frequent freezing-up of the clients, especially when surfing the web (firefox) after startup / logging in. The application freezes up for about 10-20 seconds, then everything returns to normal.
Apparently this gets better some time after starting to work, but it is annoying as hell (and keeping me from continuing to set up the remaining machines like this, as it would be a show-stopper for my wife and kids).
Note that this happens even if only one machine is accessing the /home/ directory, so it isn't about concurrent access going wrong. (Although there is a media server mounting the same share, but that one is idle 99% of the time.)
I don't really know enough about NFS and the things going on behind the scenes to know what to look for, and where. Can anyone give me a hint? Is this due to bad NFS server performance? A caching issue? How can I find out? Can this be mitigated by setting certain NFS options?