| | nfs:nfs_do_symlink_cache
| Description | Controls whether the
contents of symbolic link files are cached for NFS version 2 mounted file
systems.
| | Data Type | Integer (32-bit)
| | Default | 1 (caching enabled)
| | Range | 0 (caching disabled), 1 (caching
enabled)
| | Units | Boolean values
| | Dynamic? | Yes
| | Validation | None
| | When to Change | If a server changes
the contents of a symbolic link file without updating the modification time
stamp on the file or if the granularity of the time stamp is too large, then
changes to the contents of the symbolic link file might not be visible on
the client for extended periods. In this case, use this parameter to disable
the caching of symbolic link contents, thus making the changes visible to
applications running on the client immediately.
| | Stability Level | Evolving
|
nfs:nfs3_do_symlink_cache
| Description | Controls whether the
contents of symbolic link files are cached for NFS version 3 mounted file
systems.
| | Data Type | Integer (32-bit)
| | Default | 1 (caching enabled)
| | Range | 0 (caching disabled), 1 (caching
enabled)
| | Units | Boolean values
| | Dynamic? | Yes
| | Validation | None
| | When to Change | If a server changes
the contents of a symbolic link file without updating the modification time
stamp on the file or if the granularity of the time stamp is too large, then
changes to the contents of the symbolic link file might not be visible on
the client for extended periods. In this case, use this parameter to disable
the caching of symbolic link contents, thus making the changes visible to
applications running on the client immediately.
| | Stability Level | Evolving
|
nfs:nfs_dynamic
| Description | Controls whether a feature
known as dynamic retransmission is enabled for NFS version
2 mounted file systems using connectionless transports such as UDP. This feature
attempts to reduce retransmissions by monitoring server response times, and
then adjusting RPC timeouts and read and write transfer sizes.
| | Data Type | Integer (32-bit)
| | Default | 1 (enabled)
| | Range | 0 (disabled), 1 (enabled)
| | Dynamic? | Yes, but this parameter
is set per file system at mount time. To affect a particular file system,
unmount and mount the file system after changing this parameter.
| | Validation | None
| | When to Change | In a situation where
server response or network load varies rapidly, the dynamic retransmission
support might incorrectly increase RPC timeouts or reduce read and write transfer
sizes unnecessarily. Disabling this functionality might result in increased
throughput, but possibly, also increasing the visibility of the spikes due
to server response or network load.
| | Stability Level | Evolving
|
nfs:nfs3_dynamic
| Description | Controls whether a feature
known as dynamic retransmission is enabled for NFS version
3 mounted file systems using connectionless transports such as UDP. This feature
attempts to reduce retransmissions by monitoring server response times and
then adjusting RPC timeouts and read and write transfer sizes.
| | Data Type | Integer (32-bit)
| | Default | 0 (disabled)
| | Range | 0 (disabled), 1 (enabled)
| | Units | Boolean values
| | Dynamic? | Yes, but this parameter
is set per file system at mount time. To affect a particular file system,
unmount and mount the file system after changing this parameter.
| | Validation | None
| | When to Change | In a situation where
server response or network load varies rapidly, the dynamic retransmission
support might incorrectly increase RPC timeouts or reduce read and write transfer
sizes unnecessarily. Disabling this functionality might result in increased
throughput, but possibly, also increasing the visibility of the spikes due
to server response or network load.
| | Stability Level | Evolving
|
nfs:nfs_lookup_neg_cache
| Description | Controls whether a negative
name cache is used for NFS version 2 mounted file systems. This negative name
cache records filenames that were looked up, but not found. The cache is used
to avoid over the network lookup requests made for filenames that are already
known to not exist.
| | Data Type | Integer (32-bit)
| | Default | 1 (enabled)
| | Range | 0 (disabled), 1 (enabled)
| | Units | Boolean values
| | Dynamic? | Yes
| | Validation | None
| | When to Change | In order for the
cache to perform correctly, negative entries must be strictly verified before
they are used. This consistency mechanism is relaxed slightly for read-only
mounted file systems by assuming that the file system on the server is not
changing or is changing very slowly and that it is okay for such changes to
propagate slowly to the client. The consistency mechanism becomes the normal
attribute cache mechanism in this case.
If file systems are mounted read-only on the client, but are expected
to change on the server and these changes need to be seen immediately by the
client, then use this parameter to disable the negative cache.
| | Stability Level | Evolving
|
nfs:nfs3_lookup_neg_cache
| Description | Controls whether a negative
name cache is used for NFS version 3 mounted file systems. This negative name
cache records filenames that were looked up, but were not found. The cache
is used to avoid over-the-network lookup requests made for filenames that
are already known to not exist.
| | Data Type | Integer (32-bit)
| | Default | 1 (enabled)
| | Range | 0 (disabled), 1 (enabled)
| | Units | Boolean values
| | Dynamic? | Yes
| | Validation | None
| | When to Change | In order for the
cache to perform correctly, negative entries must be strictly verified before
they are used. This consistency mechanism is relaxed slightly for read-only
mounted file systems by assuming that the file system on the server is not
changing or is changing very slowly and that it is okay for such changes to
propagate slowly to the client. The consistency mechanism becomes the normal
attribute cache mechanism in this case.
If file systems are mounted read-only on the client, but are expected
to change on the server and these changes need to be seen immediately by the
client, then use this parameter to disable the negative cache.
| | Stability Level | Evolving
|
| |
NFS Module Parameters 
