From: Jim Rees <rees@umich.edu>
To: Max Matveev <makc@redhat.com>
Cc: linux-nfs@vger.kernel.org, steved@redhat.com
Subject: Re: [PATCH] Update nfs(5) manpage - timeo for NFS/TCP
Date: Thu, 4 Aug 2011 08:04:01 -0400 [thread overview]
Message-ID: <20110804120401.GB9984@merit.edu> (raw)
In-Reply-To: <20110804062858.EAD96813270B@regina.usersys.redhat.com>
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@redhat.com>
---
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) ...
next prev parent reply other threads:[~2011-08-04 12:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 8:11 NFS/TCP timeout sequence Max Matveev
2011-07-07 13:47 ` Trond Myklebust
2011-07-07 14:04 ` Chuck Lever
2011-07-07 14:16 ` Trond Myklebust
2011-07-07 14:44 ` Chuck Lever
2011-07-07 14:59 ` Trond Myklebust
2011-08-04 5:54 ` Max Matveev
2011-08-04 5:42 ` [PATCH] NFS: allow enough time for timeouts to run Max Matveev
2011-08-04 5:47 ` [PATCH] Update nfs(5) manpage - timeo for NFS/TCP Max Matveev
2011-08-04 12:04 ` Jim Rees [this message]
2011-08-05 0:57 ` Max Matveev
2011-08-05 1:39 ` Jim Rees
2011-08-05 2:14 ` Max Matveev
2011-07-08 6:05 ` NFS/TCP timeout sequence Max Matveev
2011-07-08 0:20 ` Max Matveev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110804120401.GB9984@merit.edu \
--to=rees@umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=makc@redhat.com \
--cc=steved@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).