NFS Performance Tuning for HP-UX 11.0 and 11i Systems

nfs performance tuning for hp-ux 11.0 and 11i systems page 63

Notes:

Page 63July 22, 2002

rpc.lockd

rpc.statd

Avoiding NFS File Lock Hangs

• Make sure hostname resolution data is accurate (i.e.

make NFS server can correctly resolve IP address of the

client – even if client is in a remote DNS domain)

• Remove corrupted files from /var/statmon/sm.bak

• Never remove files from the /var/statmon/sm

directory on only a client or server system

• Use the rpc.lockd “–C” command-line option in

heterogeneous environments

It is critical that hostname/IP address data be accurate. In the DNS case, the

potential exists for lock requests to fail when the NFS client and server reside in

different DNS domains – even if the DNS tables are accurate. This is because the

NFS client only sends it’s hostname in lock requests. Either configure search paths

for DNS or set the client’s hostname equal to the fully-qualified DNS domain name.

The files in /var/statmon/sm.bak refer to systems that rpc.statd could not

contact after a state change. If these files get corrupted (i.e. the contents of the files

don’t match the name of the file) then they should be removed during the next

maintenance window. The files in /var/stamon/sm refer to systems that

rpc.lockd has performed file locking with since the last state change. These files

should never be removed on only a client or a server. If they must be removed,

they should be removed from both systems simultaneously.

A defect in HP’s NLM implementation causes locks to hang (in a specific case)

when working with non-HP servers. The rpc.lockd “–C” option corrects this, but this

option must be enabled on all HP systems in the environment simultaneously or the

HP systems could potentially stop working correctly with each other.