General troubleshooting recommendations
From Linux NFS
Depending on your configuration, there's a number of ways that NFS can fail to work. Sometimes it can be difficult to determine exactly why it is not working. This page describes some general techniques for diagnosing the issue.
If you cannot resolve your problem and plan to report it to the developer, see Reporting bugs.
Contents |
Check server's exports
An easy first thing to doublecheck is that your server is exporting what you think it is. On the server, run the command:
exportfs -v
If you need to make modifications, edit /etc/exports and re-export using the command
exportfs -r
Remember that pseudo-filesystems in NFSv4 work very differently than NFSv3. Review the <a href="http://www.citi.umich.edu/projects/nfsv4/linux/using-nfsv4.html">Using NFSv4</a> directions if you have questions.
Check server mount functionality
Try mounting the nfs4 export on the server itself by mounting localhost:/. This will isolate whether the problem is with the server configuration.
Getting detailed debug output of the client/server interactions
Start `tcpdump -s 9000 -w /tmp/dump.out port 2049` on the client, then conduct the client/server interaction. Review the /tmp/dump.out file (or include it with your bug report).
"Reboot" the NFSv4 server without shutting down the machine
Just shut down rpc.nfsd and start it again.
I get different results when mounting via NFSv3 and NFSv4
Find a file that is differing between v3 and v4, and look at the output from the `stat` utility.
Or use `ls -lid --type-style=full-iso` and `ls -lid --time=ctime --time-style=full-iso` if you don't have stat.
