Managing NFS and KRPC Kernel Configurations in HP-UX 11i v2 (November 2013)

13
successful NFS I/O. If packets are not being dropped in the network, disabling this functionality
results in increased throughput. However, if the server response is delayed or the network is
overloaded, the number of timeouts can increase.
HP recommends leaving this tunable enabled because it helps the system minimize NFS packet loss
on congested networks.
2.1.13 nfs2_shrinkreaddir
Description
The nfs2_shrinkreaddir tunable is a solution for a defect that causes older NFS servers to incorrectly
handle NFSv2 READDIR requests with more than 1024 bytes of directory information.
Tested values
Default: 0 (Limit is not enforced and tunable is disabled)
Min: 0
Max: 1 (Limit is enforced and tunable is enabled)
Restrictions on changing
The nfs2_shrinkreaddir tunable is dynamic. System reboot is not required to activate changes made to
this tunable. Only NFSv2 mount points are affected by changing the value of this tunable.
Modifying the value
Modify this tunable only if you know or suspect that you are dealing with an older NFSv2 server that
cannot handle READDIR requests of size larger than 1K. Enable this tunable to ensure the client does
not generate a READDIR request for more than 1024 bytes of directory information. Disable the
tunable to allow the client to issue READDIR requests containing up to 8192 bytes of data.
2.1.14 nfs3_adaptive_cache_validate
Description
The nfs3_adaptive_cache_validate tunable provides a weak cache consistency (WCC) check when a
write operation is followed by a read operation. This tunable also checks for cache validation during
the read operation and before the write operation.
Tested values
Default: 0 (Weak Cache Consistency check is disabled)
Min: 0
Max: 1 (Weak Cache Consistency check is enabled)
Restrictions on changing
The nfs3_adaptive_cache_validate tunable is dynamic. System reboot is not required to activate a
change made to this tunable. Only NFSv3 mount points are affected by changing the value of this
tunable.
Note: If there are no NFS mount points in the system, any
change made to the value of the tunable is effective
immediately. If there are NFS mount points in the system, a
system reboot is required for the change to be activated.