Due to a bug in the NFS version 2 server implementation, some older NFS servers can not correctly handle NFS Version 2 READDIR requests for more than 1024 bytes of directory information in certain situations. This parameter provides a workaround in the NFS Version 2 client.

If 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, the over the wire size is set to the minimum of either the size passed in by the getdents(2) system call or NFS_MAXDATA, which is 8192 bytes.

32-bit integer

0 (disabled)

0 (disabled), 1 (enabled)

Boolean values

Yes

None

Examine the value of this parameter when using an older NFS Version 2 only server and interoperability problems occur when trying to read directories. Enabling this parameter might cause a slight performance drop to occur for applications that read directories.

Evolving

A recent change to Solaris has changed the default buffer size that the readdir(3C) library support uses from 1048 bytes to 8192 bytes. This changes the number of bytes requested through the getdents(2) system call correspondingly. This in turn, translates almost directly into larger READDIR and READDIRPLUS requests made to NFS Version 3 server. This might result in interoperability problems with server implementations that cannot handle the larger request size.

32-bit integer

0 (disabled)

0 (disabled), 1 (enabled)

Boolean values

Yes

None

Examine the value of this parameter when using an NFS Version 3 server and interoperability problems occur when trying to read directories. Enabling this parameter might cause a slight performance drop to occur for applications that read directories.

Evolving

Controls the number of TCP connections that the NFS client uses when communicating with each NFS server. The kernel RPC is constructed so that it can multiplex RPCs over a single connection, but multiple connections can be used if desired.

Integer (32-bit)

1

1 to 2³¹ - 1

Connections

Yes

None

In general, 1 connection is sufficient to achieve full network bandwidth. However, if TCP cannot utilize the bandwidth offered by the network in a single stream, then multiple connections might increase the throughput between the client and the server.

Increasing the number of connections doesn't come for free though. The price for increasing the number of connections is increased kernel resource usage to keep track of each of the connections.

Evolving

Controls the duration of time on the client that a connection between the client and server is allowed to remain idle before being closed.

Long integer (32 bits on 32-bit platforms and 64 bits on 64-bit platforms)

300,000 milliseconds (5 minutes)

0 to 2³¹ - 1 on 32-bit platforms

0 to 2⁶³ - 1 on 64-bit platforms

Milliseconds

Yes

None

Use this parameter to change the time that idle connections are allowed to exist on the client before being closed, if desired. You might might want to close connections at a faster rate to avoid consuming system resources.

Evolving

Controls the duration of time on the server that a connection between the client and server is allowed to remain idle before being closed.

Long integer (32 bits on 32-bit platforms and 64 bits on 64-bit platforms)

360,000 milliseconds (6 minutes)

0 to 2³¹ - 1 on 32-bit platforms

0 to 2⁶³ - 1 on 64-bit platforms

Milliseconds

Yes

None

Use this parameter to change the time that idle connections are allowed to exist on the server before being closed, if desired. Close connections at a faster rate to avoid consuming system resources, if desired.

Evolving