Managing NFS and KRPC Kernel Configurations in HP-UX 11i v3 (762807-001, March 2014)

Note: The nfs3_bsize tunable affects every NFSv3 filesystem.
To control the transfer sizes of specific NFS filesystems, use
the rsize and wsize mount options. Refer to the
mount_nfs(1M) man page for more information.
2.1.19 nfs3_cots_timeo
Description
The nfs3_cots_timeo tunable controls the default RPC timeout for NFSv3 mounted filesystems using a
connection-oriented transport such as TCP.
The nfs2_cots_timeo tunable controls the default RPC timeout for NFSv2 mounted filesystems. The
nfs4_cots_timeo tunable controls the default RPC timeout for NFSv4 mounted filesystems. For more
information on these tunables, see:
• nfs2_cots_timeo
• nfs4_cots_timeo
Tested Values
Default: 600 tenths of a second (1 minute)
Min: 10 tenths of a second (1 second)
Max: 36000 tenths of a second (1 hour)
Note: If the tunable is set to a value less than 10 tenths of a
second or greater than 36000 tenths of a second, an
informational warning is issued at runtime. These values are
outside the tested limits.
Restrictions on Changing
The nfs3_cots_timeo tunable is dynamic. System reboot is not required to activate changes made to
this tunable. Any change made to the value of the tunable is effective immediately. However, the
timeout duration is set per filesystem at mount time. The system administrator must unmount and re-
mount the filesystem after changing this tunable. Only NFSv3 mount points are affected by changing
the value of the nfs3_cots_timeo tunable.
Modifying the Value
If you are experiencing a large number of timeouts on connection-oriented NFSv3 filesystems,
increase the value of this tunable. However, a large number of connection-oriented timeouts can be
an indication of networking hardware or software problems.
2.1.20 nfs3_do_symlink_cache
Description
The nfs3_do_symlink_cache tunable caches the contents of symbolic links in NFSv3 mounted
filesystems. If the server changes the contents of a symbolic link, and if either the time stamps are not
updated or the granularity of the time stamp is too large, then the changes become visible to the client
after a long time interval.