From: Steve Dickson <SteveD@redhat.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/2] SUNRPC: Ensure that call_connect times out correctly
Date: Wed, 19 Mar 2014 14:22:26 -0400 [thread overview]
Message-ID: <5329E062.9030103@RedHat.com> (raw)
In-Reply-To: <1395250160.7168.1.camel@leira.trondhjem.org>
On 03/19/2014 01:29 PM, Trond Myklebust wrote:
> On Wed, 2014-03-19 at 13:10 -0400, Steve Dickson wrote:
>>
>> On 03/19/2014 11:04 AM, Trond Myklebust wrote:
>>> IOW: there is no way to make mount.nfs honour the ‘retry’ and/or ‘bg'
>>> mount options in any consistent fashion by solely relying on kernel timeouts.
>> I went back and took a look at how bg mounts worked in a number of
>> older kernels f19(3.12) all the way back to RHEL6 kernel (2.6).
>>
>> I turns out you are right. The bg mounts were not depending on
>> timeouts they were depended on the mount to fail with ECONNREFUSED
>> The very first one, which is the reason the bg mount happen
>> so fast...
>>
>> Its seems these days ECONNREFUSED are no longer return
>> as an error codes. They basically are turned into a
>> timeout... Just curious as to why ECONNREFUSED are
>> no longer returned?
>>
>> Again, thanks for the cycles!
>
> If the server is down during the initial rpc client creation, then I’d
> still expect that to fail with ECONNREFUSED due to the rpc_ping() call.
>
> Does the following patch help?
>
>
> 8<------------------------------------------------------------
> From dad628cc357a06cff8ce04300ba5c19bd92e73eb Mon Sep 17 00:00:00 2001
> From: Trond Myklebust <trond.myklebust@primarydata.com>
> Date: Wed, 19 Mar 2014 13:25:43 -0400
> Subject: [PATCH] SUNRPC: Ensure call_status() deals correctly with SOFTCONN
> tasks
>
> Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
> ---
> net/sunrpc/clnt.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/net/sunrpc/clnt.c b/net/sunrpc/clnt.c
> index cea1308a6fda..ef96568902c5 100644
> --- a/net/sunrpc/clnt.c
> +++ b/net/sunrpc/clnt.c
> @@ -2004,6 +2004,10 @@ call_status(struct rpc_task *task)
> case -EHOSTDOWN:
> case -EHOSTUNREACH:
> case -ENETUNREACH:
> + if (RPC_IS_SOFTCONN(task)) {
> + rpc_exit(task, status);
> + break;
> + }
> /*
> * Delay any retries for 3 seconds, then handle as if it
> * were a timeout.
>
No... but I do thing that patch make sense...
What's going on is-ECONNREFUSED is being seen in call_connect_status()
and the task is not a soft connection. So call_timeout() is call which
eventual times out the mount...
So just for fun I make the SETCLIENTID rpc soft, but for some
reason that didn't work either... I thought for sure it would...
steved.
next prev parent reply other threads:[~2014-03-19 18:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 18:40 [PATCH 1/2] SUNRPC: Ensure that call_connect times out correctly Trond Myklebust
2014-03-17 18:40 ` [PATCH 2/2] SUNRPC: Ensure that call_bind " Trond Myklebust
2014-03-18 19:02 ` Steve Dickson
2014-03-18 15:47 ` [PATCH 1/2] SUNRPC: Ensure that call_connect " Steve Dickson
2014-03-18 15:58 ` Trond Myklebust
2014-03-18 17:24 ` Steve Dickson
2014-03-18 18:45 ` Trond Myklebust
2014-03-18 19:00 ` Steve Dickson
2014-03-18 19:50 ` Trond Myklebust
2014-03-19 12:39 ` Steve Dickson
2014-03-19 12:52 ` Trond Myklebust
2014-03-19 14:07 ` Steve Dickson
2014-03-19 15:04 ` Trond Myklebust
2014-03-19 17:10 ` Steve Dickson
2014-03-19 17:29 ` Trond Myklebust
2014-03-19 18:22 ` Steve Dickson [this message]
2014-03-19 19:41 ` Trond Myklebust
2014-03-20 14:12 ` Steve Dickson
2014-03-20 15:19 ` Steve Dickson
2014-03-18 18:47 ` Steve Dickson
2014-03-18 18:48 ` Steve Dickson
2014-04-14 16:25 ` Jeff Layton
2014-04-14 16:57 ` Trond Myklebust
2014-04-14 17:32 ` Jeff Layton
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=5329E062.9030103@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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).