NFS Services Administrator's Guide (762805-001, March 2014)

5 Troubleshooting NFS services
This chapter describes tools and procedures for troubleshooting the NFS Services. This chapter
addresses the following topics:
• “Common problems with NFS” (page 95)
• “Performance tuning” (page 102)
• “Logging and tracing of NFS services” (page 104)
Common problems with NFS
This section lists the following common problems encountered with NFS and suggests ways to
correct them.
• “NFS “Server Not Responding” message” (page 95)
• ““Access Denied” message” (page 97)
• ““Permission Denied” message” (page 97)
• ““Device Busy” message” (page 98)
• ““Stale File Handle” message” (page 98)
• “A program hangs” (page 99)
• “Data is lost between the client and the server” (page 100)
• ““Too many levels of remote in path” message” (page 100)
NFS “Server Not Responding” message
□ Enter the /usr/sbin/ping command on the NFS client to make sure the NFS server is up
and is reachable on the network. If the ping command fails, either the server is down, or the
network has a problem. If the server is down, reboot it, or wait for it to come back up. For
more information on troubleshooting network problems, see HP-UX LAN Administrator's Guide.
□ Ensure that the following daemons are running on the NFS server:
rpc.mountd◦
◦ rpc.statd
◦ rpc.lockd
□ Enter the following command on the NFS client to make sure the server is running all the NFS
server processes:
/usr/bin/rpcinfo -p servername
The rpcinfo command should display the following services:
◦ rpcbind
◦ nfs
◦ mountd
◦ status
◦ nlockmgr
Common problems with NFS 95