All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Jan Engelhardt <jengelh-nopoi9nDyk+ELgA04lAiVw@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: mount.nfs4 hangs when rpcbind is not reachable
Date: Fri, 23 Apr 2010 11:32:02 -0400	[thread overview]
Message-ID: <4BD1BD72.2030709@oracle.com> (raw)
In-Reply-To: <alpine.LSU.2.01.1004231717180.2242-SHaQjdQMGhDmsUXKMKRlFA@public.gmane.org>

On 04/23/2010 11:18 AM, Jan Engelhardt wrote:
> Hi,
>
>
> I just noticed that in a diskless-system initramfs, mount.nfs4 appears
> to hang whenever it cannot get a response (any response) from the
> rpcbind port. If there is no rpcbind running and thus, TCP RST is sent,
> fine. But if it's dropped, like when the "lo" device is not in the "up"
> state (as can easily happen at this stage of boot), mount.nfs4 waits
> forever.

The rpcbind registration RPC request is "hard".  Maybe it should be "soft".

But a better question is why are you doing an NFS mount if "lo" is not 
up?  NFS has never worked in this case, because there would be no way 
for the kernel to communicate with user space.

-- 
chuck[dot]lever[at]oracle[dot]com

  parent reply	other threads:[~2010-04-23 15:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23 15:18 mount.nfs4 hangs when rpcbind is not reachable Jan Engelhardt
     [not found] ` <alpine.LSU.2.01.1004231717180.2242-SHaQjdQMGhDmsUXKMKRlFA@public.gmane.org>
2010-04-23 15:32   ` Chuck Lever [this message]
2010-04-23 15:53     ` Jan Engelhardt
     [not found]       ` <alpine.LSU.2.01.1004231750380.20942-SHaQjdQMGhDmsUXKMKRlFA@public.gmane.org>
2010-04-23 16:03         ` Chuck Lever
2010-04-23 16:25           ` Jan Engelhardt
2010-04-23 17:00             ` Chuck Lever
2010-04-23 17:39               ` Jan Engelhardt
2010-04-23 18:04                 ` Chuck Lever

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=4BD1BD72.2030709@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=jengelh-nopoi9nDyk+ELgA04lAiVw@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.