NFS/TCP does linear backoff then retransmiting - the manpage was mistakenly asserting the "no backoff" theory. Signed-off-by: Max Matveev <makc@xxxxxxxxxx> Signed-off-by: Jim Rees <rees@xxxxxxxxx> --- utils/mount/nfs.man | 16 ++++++++++------ 1 files changed, 10 insertions(+), 6 deletions(-) diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man index be91a25..ff0ed60 100644 --- a/utils/mount/nfs.man +++ b/utils/mount/nfs.man @@ -113,12 +113,16 @@ option may mitigate some of the risks of using the option. .TP 1.5i .BI timeo= n -The time (in tenths of a second) the NFS client waits for a -response before it retries an NFS request. If this -option is not specified, requests are retried every -60 seconds for NFS over TCP. -The NFS client does not perform any kind of timeout backoff -for NFS over TCP. +The time in deciseconds (tenths of a second) the NFS client waits for a +response before it retries an NFS request. +.IP +For NFS over TCP the default +.B timeo +value is 600 (60 seconds). +The NFS client performs linear backoff: After each retransmission the +timeout is increased by +.BR timeo +up to the maximum of 600 seconds. .IP However, for NFS over UDP, the client uses an adaptive algorithm to estimate an appropriate timeout value for frequently used -- 1.7.4.4 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
