public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: nfs@lists.sourceforge.net
Subject: Re: NFS server not responding
Date: Thu, 04 Dec 2003 14:11:37 -0500	[thread overview]
Message-ID: <3FCF86E9.2030300@RedHat.com> (raw)
In-Reply-To: <shsr7zk5sw4.fsf@guts.uio.no>

[-- Attachment #1: Type: text/plain, Size: 769 bytes --]

Trond Myklebust wrote:

>>>>>>" " == Steve Dickson <SteveD@redhat.com> writes:
>>>>>>            
>>>>>>
>
>     >     linux-2.4.20-nfs-ia64-EIO.patch - increase RPC_RTO_MIN to
>     >     HZ/30
>
>Err.. That's a decrease...
>  
>
Well... it was in increase at the time I posted the patch.
If remember correctly... there was actually some discussion
that 1/30th of a second was a bit too long...

>You are setting the minimum timeout value at 1/30th of a second
>instead of 1/10th of a second.
>  
>
Right... I did miss this "minor" detail when I did the port....

>This might indeed explain why people are seeing an increase in resends
>and 'server not responding' messages.
>  
>
Most definitely... Here is the patch that should take care of the problem...

SteveD.


[-- Attachment #2: linux-2.4.33-nfs-rtomin.patch --]
[-- Type: text/plain, Size: 336 bytes --]

--- linux-2.4.22/net/sunrpc/timer.c.org	2003-12-04 10:47:01.000000000 -0500
+++ linux-2.4.22/net/sunrpc/timer.c	2003-12-04 13:46:01.000000000 -0500
@@ -8,7 +8,7 @@
 
 #define RPC_RTO_MAX (60*HZ)
 #define RPC_RTO_INIT (HZ/5)
-#define RPC_RTO_MIN (HZ/30)
+#define RPC_RTO_MIN (HZ/10)
 
 void
 rpc_init_rtt(struct rpc_rtt *rt, long timeo)

  reply	other threads:[~2003-12-04 19:10 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-27 12:00 NFS server not responding Douglas Furlong
2003-11-27 16:30 ` Trond Myklebust
2003-11-27 19:07   ` Douglas Furlong
2003-11-27 20:02     ` Trond Myklebust
2003-11-28  8:46 ` Juergen Sauer
2003-11-28  9:37   ` Douglas Furlong
2003-11-28 10:11     ` Juergen Sauer
2003-11-28 10:48       ` Douglas Furlong
2003-11-28 12:28         ` Bogdan Costescu
2003-11-28 16:56           ` Trond Myklebust
2003-11-28 18:43             ` Bogdan Costescu
2003-12-02 14:37             ` Douglas Furlong
2003-12-02 15:37               ` Trond Myklebust
2003-12-04 17:17                 ` Steve Dickson
2003-12-04 17:37             ` Steve Dickson
2003-12-04 18:39               ` Trond Myklebust
2003-12-04 19:11                 ` Steve Dickson [this message]
2003-12-04 20:55                   ` seth vidal
2003-12-04 21:24                     ` Steve Dickson
2003-12-05  2:53                       ` Kyle Rose
2003-12-09 19:47                         ` Steve Dickson
2003-12-09 20:09                           ` Kyle Rose
2003-12-05 15:50                 ` Bogdan Costescu
2003-11-30 20:01           ` seth vidal
2003-12-01 10:58             ` Bogdan Costescu
2003-11-28 12:36       ` Bogdan Costescu
  -- strict thread matches above, loose matches on Subject: below --
2009-05-16  0:57 nfs: " Jerome Walters

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=3FCF86E9.2030300@RedHat.com \
    --to=steved@redhat.com \
    --cc=nfs@lists.sourceforge.net \
    /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