| soft/hard |
If the system is mounted in the soft mount mode, if the NFS request times out, the client returns an error to the calling program; if the hard connection method is used, the client keeps re-requesting until it succeeds. The default is hard. |
For key data services, you do not want the service to be interrupted due to network delays, server service restarts, or short-term overloads. It is recommended to use the hard parameter when mounting; for non-critical data services, you want the client program to respond as soon as possible, you can use the soft parameter . |
| fear = n |
The amount of time the client waits before retransmitting the request. For TCP-based NFS services, the default waiting time for retransmission is 60s. When using the TCP protocol, the NFS Client does not perform any timeout backoff. For the UDP protocol, the client uses an appropriate algorithm to estimate appropriate timeouts for commonly used request types. But use the timeo setting for less commonly used request types. If timeo is not set, uncommon request types are retried after 1.1 seconds. After each retransmission, NFS Client will double the timeout time, up to a maximum of 60 seconds. |
The selection of the two parameters timeo and retrans** mainly depends on the network performance. For situations where the network throughput is small, the delay is high, the jitter is high, and the packet loss rate is high, it is recommended to set the timeo and retrans parameters to be larger. For the case of large network throughput, low delay, low jitter, and low packet loss rate |