This section (see Table 5-2) shows potential client bottlenecks and how to remedy them.
Table 5-2 Client Bottlenecks
Symptom(s) |
Command/Tool |
Cause |
Solution |
---|---|---|---|
NFS server hostname not responding or slow response to commands when using NFS-mounted directories |
nfsstat |
User's path variable |
List directories on local file systems first, critical directories on remote file systems second, and then the rest of the remote file systems. |
NFS server hostname not responding or slow response to commands when using NFS-mounted directories |
nfsstat |
Running executable from an NFS-mounted file system |
Copy the application locally (if used often). |
NFS server hostname not responding; badxid >5% of total calls and badxid = timeout |
nfsstat -rc |
Client times out before server responds |
Check for server bottleneck. If the server's response time isn't improved, increase the timeo parameter in the /etc/vfstab file of clients. Try increasing timeo to 25, 50, 100, 200 (tenths of seconds). Wait one day between modifications and check to see if the number of time-outs decreases. |
badxid = 0 |
nfsstat -rc |
Slow network |
Increase rsize and wsize in the /etc/vfstab file. Check interconnection devices (bridges, routers, gateways). |