NFS Services Administrator's Guide (B.11.31.03) August 2008

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.
□ If you have a small number of NFS applications that require absolute data integrity,
add the O_SYNC flag to the open() calls in your applications. When you open a
file with the O_SYNC flag, a write() call will not return until the write request
Common Problems with NFS 135