From patchwork Thu Aug 4 05:47:33 2011 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Max Matveev X-Patchwork-Id: 1033932 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by demeter2.kernel.org (8.14.4/8.14.4) with ESMTP id p746T4cK011971 for ; Thu, 4 Aug 2011 06:29:04 GMT Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750984Ab1HDG3C (ORCPT ); Thu, 4 Aug 2011 02:29:02 -0400 Received: from mx1.redhat.com ([209.132.183.28]:45958 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750951Ab1HDG3B (ORCPT ); Thu, 4 Aug 2011 02:29:01 -0400 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p746T12J025982 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 4 Aug 2011 02:29:01 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p746T1Ba023915; Thu, 4 Aug 2011 02:29:01 -0400 Received: from regina.usersys.redhat.com (dhcp-176-225.mel.redhat.com [10.64.176.225]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id p746Sxjw029490; Thu, 4 Aug 2011 02:29:00 -0400 Received: by regina.usersys.redhat.com (Postfix, from userid 500) id EAD96813270B; Thu, 4 Aug 2011 16:28:58 +1000 (EST) In-Reply-To: <20026.13331.411712.805796@regina.usersys.redhat.com> References: <20026.13331.411712.805796@regina.usersys.redhat.com> From: Max Matveev Date: Thu, 4 Aug 2011 15:47:33 +1000 Subject: [PATCH] Update nfs(5) manpage - timeo for NFS/TCP To: linux-nfs@vger.kernel.org Cc: steved@redhat.com Message-Id: <20110804062858.EAD96813270B@regina.usersys.redhat.com> X-Scanned-By: MIMEDefang 2.67 on 10.5.11.12 Sender: linux-nfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.6 (demeter2.kernel.org [140.211.167.43]); Thu, 04 Aug 2011 06:29:04 +0000 (UTC) NFS/TCP does linear backoff then retransmiting - the manpage was mistakenly asserting the "no backoff" theory. Signed-off-by: Max Matveev --- 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. .IP However, for NFS over UDP, the client uses an adaptive algorithm to estimate an appropriate timeout value for frequently used