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

directory, so one user cannot remove files another user is accessing. For more
information on the source code control system, see rcsintro(5).
□ If someone has restored the server’s file systems from backup or entered the
fsirand command on the server, follow these steps on each of the NFS clients to
prevent stale file handles by restarting NFS:
1. Enter the mount(1M) command with no options, to get a list of all the mounted
file systems on the client:
/usr/sbin/mount
2. For every NFS-mounted directory listed by the mount command, enter the
following command to determine whether the directory is currently in use:
/usr/sbin/fuser -cu local_mount_point
This command lists the process IDs and user names of everyone using the
mounted directory.
3. Warn any users to cd out of the directory, and kill any processes that are using
the directory, or wait until the processes terminate. Enter the following
command to kill all processes using the directory:
/usr/sbin/fuser -ck local_mount_point
4. Enter the following command on the client to unmount all NFS-mounted
directories:
/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 129).
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
134 Troubleshooting NFS Services