I applied this article to my server today and I found an exportfs-error: in /etc/exports a range of clients has to be described like 'ip/netmask'. CORRECT WAY: '192.168.0.0/255.255.255.0', whereas the example on this page throws an error.--Zenlord 08:34, 30 September 2009 (EDT)
Since NFSv4 is a insecure protocol (doesn't encrypt traffic), what about adding some info about tunneling it with SSH? This link is very useful: http://blogs.sun.com/shepler/entry/tunneling_nfs_traffic_via_ssh The only problem, rpcbind has to be also tunneled.
client ip address/ranges
Also mentioning that we need to put client ip address/ranges in the /etc/exports might be a good idea for people using NFS for the first time. Inxsible
Mounting the partitions on the client
I tried following the wiki but it seems that, for the client, it is no longer necessary to start rpcbind or nfs-common services.--Angheloko 11:44, 8 October 2011 (EDT)
Unmounting non-api filesystems hangs
I've figured out that if you don't add netfs to daemons in /etc/rc.conf (because you mount nfs shares manually) shutting down will hang with "Unmounting non-api filesystems". Adding netfs to daemons fixes that.
Maybe that should be added to the troubleshooting section?
I would be happy to add it. A bit of googling indicates that I'm not the first one who's had that problem.