Troubleshooting and tuning NFS

Improving access time

If access to remote files seems unusually slow, enter the following command:

ps -ef

on the server and look for abnormal (high) execution times for NFS daemon processes to check that the access time is not being affected adversely by a runaway daemon. If there is nothing unusual (processes with excessive CPU time) in the display, and other clients are getting good response, make sure your biod daemons are running. At the client, type the following command:

ps -ef | grep biod

Look for biod daemons in the display, then enter the command again. If the biods do not accumulate excessive CPU time, they are probably hung. If they are dead or hung, follow these steps:

  1. Determine the process ID numbers of the daemon processes:

    ps -ef | grep biod

    The second field contains the process ID number.

  2. Enter the following command to kill the processes:

    kill -9 pid

    where pid is the process ID of the biod daemon.

  3. Restart the biod daemon by typing:


If biod is running, check your network connection. The netstat -i command can help you determine if you are dropping packets; for more information, see netstat(ADMN).
Next topic: Mount error messages
Previous topic: Using NFS with Netscape

© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 - 01 June 2005