Max Matveev wrote: NFS/TCP does linear backoff then retransmiting - the manpage was mistakenly asserting the "no backoff" theory. Signed-off-by: Max Matveev <makc@xxxxxxxxxx> --- utils/mount/nfs.man | 14 +++++++++----- 1 files changed, 9 insertions(+), 5 deletions(-) diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man index be91a25..7681b10 100644 --- a/utils/mount/nfs.man +++ b/utils/mount/nfs.man @@ -114,11 +114,15 @@ 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. +response before it retries an NFS request. +.IP +For NFS over TCP the default +.B timeo +value is 600 which equals to 60 seconds. +The NFS client performs linear backoff - +after each retransmission the timeout is increased by +.BR timeo /10 +seconds upto the maximum of 600 seconds. "upto" should be "up to". I'm not crazy about the wording. How about For NFS over TCP the default timeo is 600 (60 seconds). The NFS client performs linear backoff. After each retransmission the timeout is increased by timeo up to the maximum of 600 seconds. Finally, I would call them "deciseconds". timeo: The time in deciseconds (tenths of a second) ... -- 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
