| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Solaris Tunable Parameters Reference Manual |
1. Overview of Oracle Solaris System Tuning
2. Oracle Solaris Kernel Tunable Parameters
Where to Find Tunable Parameter Information
nfs:nfs3_pathconf_disable_cache
nfs:nfs4_pathconf_disable_cache
nfs:nfs_write_error_to_cons_only
nfs:nfs3_max_transfer_size_clts
nfs:nfs3_max_transfer_size_cots
rpcmod:svc_default_max_same_xprt
4. Internet Protocol Suite Tunable Parameters
5. Network Cache and Accelerator Tunable Parameters
A. Tunable Parameters Change History
This section describes NFS parameters for the nfssrv module.
Controls some security checking that the NFS server attempts to do to enforce integrity on the part of its clients. The NFS server can check whether the source port from which a request was sent was a reserved port. A reserved port has a number less than 1024. For BSD-based systems, these ports are reserved for processes being run by root. This security checking can prevent users from writing their own RPC-based applications that defeat the access checking that the NFS client uses.
Integer (32-bit)
0 (security checking disabled)
0 (security checking disabled) or 1 (security checking enabled)
Boolean values
Yes
None
Use this parameter to prevent malicious users from gaining access to files by using the NFS server that they would not ordinarily have access to. However, the reserved port notion is not universally supported. Thus, the security aspects of the check are very weak. Also, not all NFS client implementations bind their transport endpoints to a port number in the reserved range. Thus, interoperability problems might result if the security checking is enabled.
Unstable
Controls the behavior of the NFS version 2 server when it processes WRITE requests. The NFS version 2 protocol mandates that all modified data and metadata associated with the WRITE request reside on stable storage before the server can respond to the client. NFS version 2 WRITE requests are limited to 8192 bytes of data. Thus, each WRITE request might cause multiple small writes to the storage subsystem. This can cause a performance problem.
One method to accelerate NFS version 2 WRITE requests is to take advantage of a client behavior. Clients tend to send WRITE requests in batches. The server can take advantage of this behavior by clustering together the different WRITE requests into a single request to the underlying file system. Thus, the data to be written to the storage subsystem can be written in fewer, larger requests. This method can significantly increase the throughput for WRITE requests.
Integer (32-bit)
1 (clustering enabled)
0 (clustering disabled) or 1 (clustering enabled)
Boolean values
Yes
None
Some very small NFS clients, particularly PC clients, might not batch WRITE requests. Thus, the behavior required from the clients might not exist. In addition, the clustering in the NFS version 2 server might just add overhead and slow down performance instead of increasing it.
Unstable
Controls the size of the cache of client handles that contact the NFS authentication server. This server authenticates NFS clients to determine whether they are allowed access to the file handle that they are trying to use.
Integer (32-bit)
16
0 to 231 - 1
Client handles
Yes
None
This cache is not dynamic, so attempts to allocate a client handle when all are busy will fail. This failure results in requests being dropped by the NFS server because they could not be authenticated. Most often, this result is not a problem because the NFS client just times out and retransmits the request. However, for soft-mounted file systems on the client, the client might time out, not retry the request, and then return an error to the application. This situation might be avoided if you ensure that the size of the cache on the server is large enough to handle the load.
Unstable
Controls the duration of time that entries are held in the NFS authentication cache before being purged due to memory pressure in the system.
Long integer (32 bits on 32-bit platforms and 64 bits on 64-bit platforms)
3600 seconds (1 hour)
0 to 231 - 1 on 32-bit platforms
0 to 263 - 1 on 64-bit platforms
Seconds
Yes
None
The size of the NFS authentication cache can be adjusted by varying the minimum age of entries that can get purged from the cache. The size of the cache should be controlled so that it is not allowed to grow too large, thus using system resources that are not allowed to be released due to this aging process.
Unstable
|