From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: EACCES in mount.nfs
Date: Mon, 05 May 2008 08:24:02 -0400 [thread overview]
Message-ID: <481EFC62.9030808@RedHat.com> (raw)
In-Reply-To: <183E9EC8-78F5-4352-BB01-84F9CE4F72FE@oracle.com>
Sorry for the delayed response... I spent most of last week
off line due to Red Hat moving to a new building... fun, fun, fun! :-\
Chuck Lever wrote:
> Hi Steve-
>
> There is an important case in mount.nfs where EACCES is temporary: The
> kernel's rpcbind client returns EACCES if the remote rpcbind server
> replies that the requested service is not registered.
I guess I see the reasoning behind this... a server could be coming
up so the mount should hang around waiting for that...
>
> It would be easy enough for the kernel's mount client to remap that
> error code into something unique for the mount system call.
I would think ENOENT would be a better mapping for RPC_PROG_UNAVAIL.
But that still leaves the possible problem of the mount not waiting
around for servers to come up... Or do we even have to worry about
mounts failing because a server is not up yet? I'm beginning to
think not...
steved.
prev parent reply other threads:[~2008-05-05 12:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 21:42 EACCES in mount.nfs Chuck Lever
2008-05-05 12:24 ` Steve Dickson [this message]
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=481EFC62.9030808@RedHat.com \
--to=steved@redhat.com \
--cc=chuck.lever@oracle.com \
--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