| | nfs:nfs_shrinkreaddir
| Description | Some older NFS servers
might incorrectly handle NFS version 2 READDIR requests
for more than 1024 bytes of directory information. This is due to a bug in
the server implementation. However, this parameter contains a workaround in
the NFS version 2 client.
When this parameter is enabled, the client does not generate a READDIR request for larger than 1024 bytes of directory information.
If this parameter is disabled, then the over-the-wire size is set to the minimum
of either the size passed in by using the getdents(2) system call or by using NFS_MAXDATA, which is 8192 bytes.
| | Data Type | Integer (32-bit)
| | Default | 0 (disabled)
| | Range | 0 (disabled), 1 (enabled)
| | Units | Boolean values
| | Dynamic? | Yes
| | Validation | None
| | When to Change | Examine the value
of this parameter if an older NFS version 2 only server is used and interoperability
problems are seen when trying to read directories. Enabling this parameter
might cause a slight performance drop for applications that read directories.
| | Stability Level | Evolving
|
nfs:nfs_write_error_interval
| Description | Controls the time duration
in between logging ENOSPC and EDQUOT
write errors seen by the NFS client. It affects both NFS version 2 and 3 clients.
| | Data Type | Long integer (32 bits
on 32-bit platforms and 64 bits on 64-bit platforms)
| | Default | 5 seconds
| | Range | 0 to 231
- 1 on 32-bit platforms
0 to 263 - 1 on 64-bit platforms
| | Units | Seconds
| | Dynamic? | Yes
| | Validation | None
| | When to Change | Increase or decrease
the value of this parameter in response to the volume of messages being logged
by the client. Typically, you might want to increase the value of this parameter
to decrease the number of out of space messages being
printed when a full file system on a server is being actively used.
| | Stability Level | Evolving
|
nfs:nfs_write_error_to_cons_only
| Description | Controls whether NFS
write errors are logged to the system console and syslog
or to the system console only. It affects messages for both NFS version 2
and 3 clients.
| | Data Type | Integer (32-bit)
| | Default | 0 (system console and syslog)
| | Range | 0 (system console and syslog), 1 (system console)
| | Units | Boolean values
| | Dynamic? | Yes
| | Validation | None
| | When to Change | Examine the value
of this parameter to avoid filling up the file system containing the messages
logged by the syslogd(1M) daemon. When this parameter is
enabled, messages are printed on the system console only and are not copied
to the syslog messages file.
| | Stability Level | Evolving
|
nfs:nfs_disable_rddir_cache
| Description | Controls the use of
a cache to hold responses from NFS version 2 READDIR and
NFS Version 3 READDIR and READDIRPLUS
requests. This cache avoids over-the-wire calls to the server to retrieve
directory information.
| | Data Type | Integer (32-bit)
| | Default | 0 (caching enabled)
| | Range | 0 (caching enabled), 1 (caching
disabled)
| | Units | Boolean values
| | Dynamic? | Yes
| | Validation | None
| | When to Change | Examine the value
of this parameter if interoperability problems develop due to a server that
does not update the modification time on a directory when a file or directory
is created in it or removed from it. The symptoms are that new names do not
appear in directory listings after they have been added to the directory or
that old names do not disappear after they have been removed from the directory.
This parameter controls the caching for both NFS version 2 and 3 mounted
file systems. This parameter applies to all NFS mounted file systems, so caching
cannot be disabled or enabled on a per file system basis.
| | Stability Level | Evolving
|
nfs:nfs3_bsize
| Description | Controls the logical
block size used by the NFS version 3 client. This block size represents the
amount of data that the client attempts to read from or write to the server
when it needs to do an I/O.
| | Data Type | Unsigned integer (32-bit)
| | Default | 32,768 (32 Kbytes)
| | Range | 0 to 231
- 1
| | Units | Bytes
| | Dynamic? | Yes, but the block size
for a file system is set when the file system is mounted. To affect a particular
file system, unmount and mount the file system after changing this parameter.
| | Validation | None. Setting this parameter
too low or too high might cause the system to malfunction. Do not set this
parameter to anything less than PAGESIZE for the specific
platform. Do not set this parameter too high because it might cause the system
to hang waiting for memory allocations to be granted.
| | When to Change | Examine the value
of this parameter when attempting to change the maximum data transfer size.
Change this parameter in conjunction with the nfs3_max_transfer_size parameter. If larger transfers are desired, increase both parameters.
If smaller transfers are desired, then just reducing this parameter should
suffice.
| | Stability Level | Unstable
|
| |
