NFS Services Administrator Guide (5900-3045, March 2013)

/usr/sbin/umount -aF nfs
5. Enter the following commands to restart the NFS client:
/sbin/init.d/nfs.client stop
/sbin/init.d/nfs.client start
A Program Hangs
□ Check whether the NFS server is up and operating correctly. If you are not sure, see “NFS
“Server Not Responding” Message” (page 94).
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, enter 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 nlockmgr
/usr/bin/rpcinfo -u clientname status
/usr/bin/rpcinfo -u clientname nlockmgr
If any of these commands return RPC_TIMED_OUT, the rpc.statd or rpc.lockd process
may be hung. Follow these steps to restart rpc.statd and rpc.lockd daemons:
1. Enter 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. Enter 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.
3. Enter the following commands to verify that rpc.statd, rpc.lockd, and nfsd are
all running and responding to RPC requests:
/usr/bin/rpcinfo -u servername status
/usr/bin/rpcinfo -u servername nlockmgr
/usr/bin/rpcinfo -u servername nfs
/usr/bin/rpcinfo -u clientname status
/usr/bin/rpcinfo -u clientname nlockmgr
/usr/bin/rpcinfo -u clientname nfs
4. Before retrying the mount that caused the program to hang, wait for a short while, say
two minutes.
5. If the problem persists, restart rpc.statd and rpc.lockd daemons and enable tracing.
Data is Lost Between the Client and the Server
□ Make sure that the directory is not exported from the server with the async option. If the
directory is exported with the async option, the NFS server will acknowledge NFS writes
before actually writing data to disk.
□ If users or applications are writing to the NFS-mounted directory, make sure it is mounted with
the hard option (the default), rather than the soft option.
98 Troubleshooting NFS Services