public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever-MouhYhfBpPxXrIkS9f7CXA@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/2] mount: ECONNREFUSED is a permanent error
Date: Fri, 09 Oct 2009 09:16:50 -0400	[thread overview]
Message-ID: <4ACF37C2.6030208@RedHat.com> (raw)
In-Reply-To: <20091008173703.12619.35788.stgit-RytpoXr2tKZ9HhUboXbp9zCvJB+x5qRC@public.gmane.org>



On 10/08/2009 01:37 PM, Chuck Lever wrote:
> I had assumed early on that mount.nfs should retry a refused connection.
> 
> Apparently this is not the case.  Legacy mount.nfs4 fails immediately
> if the NFS server refuses the connection.  Legacy mount.nfs and
> text-based mount.nfs both fail immediately if the rpcbind service is
> refusing connections.
> 
What about if the server is on the way up (i.e the network is up)
but has not started the NFS service? In that window, the server will 
return ECONNREFUSED since nobody is listening, but in a very short time
there will be a listener... The mount should not fail in that case...

steved.
 

  parent reply	other threads:[~2009-10-09 13:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-08 17:36 [PATCH 0/2] Two minor bug fixes Chuck Lever
     [not found] ` <20091008173520.12619.10662.stgit-RytpoXr2tKZ9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2009-10-08 17:37   ` [PATCH 1/2] mount: ECONNREFUSED is a permanent error Chuck Lever
     [not found]     ` <20091008173703.12619.35788.stgit-RytpoXr2tKZ9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2009-10-09 13:16       ` Steve Dickson [this message]
     [not found]         ` <4ACF37C2.6030208-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-10-09 15:13           ` Chuck Lever
     [not found]             ` <DDBA069F-E9B8-4BE3-B13C-2B69406C3C9A-MouhYhfBpPxXrIkS9f7CXA@public.gmane.org>
2009-10-09 15:20               ` Steve Dickson
     [not found]                 ` <4ACF54B4.9020900-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-10-09 15:45                   ` Chuck Lever
2009-10-09 16:33                     ` Ian Kent
2009-11-16 18:13       ` Steve Dickson
     [not found]         ` <4B019664.3020002-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-11-16 18:16           ` Chuck Lever
     [not found]             ` <E5331E4C-EE5B-4C60-9330-1B81F2FA065B-MouhYhfBpPxXrIkS9f7CXA@public.gmane.org>
2009-11-16 19:47               ` Steve Dickson
2009-10-08 17:37   ` [PATCH 2/2] mount.nfs: Assume v2/v3 if mount-related options are present Chuck Lever
     [not found]     ` <20091008173712.12619.45807.stgit-RytpoXr2tKZ9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2009-10-08 17:45       ` Trond Myklebust
     [not found]         ` <1255023929.11961.7.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-10-08 17:51           ` Chuck Lever
2009-10-09 13:29       ` Steve Dickson
     [not found]         ` <4ACF3AD1.2080802-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-10-09 15:03           ` Chuck Lever
2009-10-09 15:12             ` Steve Dickson
     [not found]               ` <4ACF52E2.6060501-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-10-09 15:18                 ` Chuck Lever
2009-11-16 17:54       ` Steve Dickson

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=4ACF37C2.6030208@RedHat.com \
    --to=steved@redhat.com \
    --cc=chuck.lever-MouhYhfBpPxXrIkS9f7CXA@public.gmane.org \
    --cc=linux-nfs@vger.kernel.org \
    /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