NFS Services Administrator's Guide (B.11.31.04) March 2009

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 127)
• “Performance Tuning” (page 135)
• “Logging and Tracing of NFS Services” (page 138)
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 127)
• ““Access Denied” Message” (page 129)
• ““Permission Denied” Message” (page 129)
• ““Device Busy” Message” (page 130)
• ““Stale File Handle” Message” (page 131)
• “A Program Hangs” (page 132)
• “Data is Lost Between the Client and the Server” (page 133)
• ““Too Many Levels of Remote in Path” Message” (page 134)
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
Common Problems with NFS 127