NFS Services Administrator's Guide

Troubleshooting NFS Services
Common Problems with NFS
Chapter 8 301
If a Program Hangs
❏ Check whether the NFS server is up and operating correctly. See “If
You Receive an NFS “Server Not Responding” Message” on page 290.
If the server is down, wait until it comes back up, or, if the directory
was mounted with the intr mount option (the default), you can
interrupt the NFS mount, usually with CTRL-C.
❏ If the program uses file locking, issue the following commands (on
either the client or the server) to make sure rpc.statd and
rpc.lockd are available and responding to RPC requests:
/usr/bin/rpcinfo -u servername status
/usr/bin/rpcinfo -u servername llockmgr
/usr/bin/rpcinfo -u servername nlockmgr
/usr/bin/rpcinfo -u clientname status
/usr/bin/rpcinfo -u clientname llockmgr
/usr/bin/rpcinfo -u clientname nlockmgr
If any of these commands returns RPC_TIMED_OUT, the rpc.statd or
rpc.lockd process may be hung. Follow these steps to restart
rpc.statd and rpc.lockd:
1. Issue the following commands, on both the NFS client and the
NFS server, to kill rpc.statd and rpc.lockd (PID is a process
ID returned by the ps command):
/usr/bin/ps -ef | /usr/bin/grep rpc.statd
/usr/bin/kill PID
/usr/bin/ps -ef | /usr/bin/grep rpc.lockd
/usr/bin/kill PID
2. Issue the following commands, on both the client and the server,
to remove the contents of the sm and sm.bak directories:
/usr/bin/rm -r /etc/sm
/usr/bin/rm -r /etc/sm.bak
3. Issue the following commands to restart rpc.statd and
rpc.lockd on both the client and the server:
/usr/sbin/rpc.statd
/usr/sbin/rpc.lockd
NOTE Always start rpc.statd before starting rpc.lockd.