From: Trond Myklebust <trondmy@hammerspace.com>
To: "chuck.lever@oracle.com" <chuck.lever@oracle.com>,
"trondmy@kernel.org" <trondmy@kernel.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"bfields@redhat.com" <bfields@redhat.com>
Subject: Re: [PATCH v2 10/10] nfsd: Ignore rpcbind errors on nfsd startup
Date: Sun, 19 Dec 2021 20:49:50 +0000 [thread overview]
Message-ID: <3167a9a815ac9c82700bd58d8c421de31eee8b91.camel@hammerspace.com> (raw)
In-Reply-To: <831659F6-3005-459B-92ED-933BBCEE6FE9@oracle.com>
On Sun, 2021-12-19 at 18:15 +0000, Chuck Lever III wrote:
>
> > On Dec 18, 2021, at 8:38 PM, trondmy@kernel.org wrote:
> >
> > From: Trond Myklebust <trond.myklebust@hammerspace.com>
> >
> > NFSv4 doesn't need rpcbind, so let's not refuse to start up just
> > because
> > the rpcbind registration failed.
>
> Commit 7e55b59b2f32 ("SUNRPC/NFSD: Support a new option for ignoring
> the result of svc_register") added vs_rpcb_optnl, which is already
> set for nfsd4_version4. Is that not adequate?
>
The other issue is that under certain circumstances, you may also want
to run NFSv3 without rpcbind support. For instance, when you have a
knfsd server instance running as a data server, there is typically no
need to run rpcbind.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2021-12-19 20:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-19 1:37 [PATCH v2 00/10] Assorted patches for knfsd trondmy
2021-12-19 1:37 ` [PATCH v2 01/10] nfsd: map EBADF trondmy
2021-12-19 1:37 ` [PATCH v2 02/10] nfsd: Add errno mapping for EREMOTEIO trondmy
2021-12-19 1:37 ` [PATCH v2 03/10] nfsd: Retry once in nfsd_open on an -EOPENSTALE return trondmy
2021-12-19 1:37 ` [PATCH v2 04/10] nfsd: Distinguish between required and optional NFSv3 post-op attributes trondmy
2021-12-19 1:37 ` [PATCH v2 05/10] nfs: Add export support for weak cache consistency attributes trondmy
2021-12-19 1:37 ` [PATCH v2 06/10] nfsd: NFSv3 should allow zero length writes trondmy
2021-12-19 1:38 ` [PATCH v2 07/10] nfsd: Add a tracepoint for errors in nfsd4_clone_file_range() trondmy
2021-12-19 1:38 ` [PATCH v2 08/10] nfsd: Replace use of rwsem with errseq_t trondmy
2021-12-19 1:38 ` [PATCH v2 09/10] nfsd: allow lockd to be forcibly disabled trondmy
2021-12-19 1:38 ` [PATCH v2 10/10] nfsd: Ignore rpcbind errors on nfsd startup trondmy
2021-12-19 18:15 ` Chuck Lever III
2021-12-19 20:49 ` Trond Myklebust [this message]
2021-12-20 15:51 ` Chuck Lever III
2021-12-20 18:35 ` Trond Myklebust
2021-12-20 19:02 ` Chuck Lever III
2021-12-20 19:52 ` Trond Myklebust
2021-12-20 20:12 ` Chuck Lever III
2021-12-19 18:34 ` [PATCH v2 09/10] nfsd: allow lockd to be forcibly disabled Chuck Lever III
2021-12-21 18:14 ` [PATCH v2 07/10] nfsd: Add a tracepoint for errors in nfsd4_clone_file_range() Chuck Lever III
2021-12-19 20:11 ` [PATCH v2 06/10] nfsd: NFSv3 should allow zero length writes Chuck Lever III
2022-01-05 16:10 ` [PATCH v2 05/10] nfs: Add export support for weak cache consistency attributes Daire Byrne
2021-12-19 20:10 ` [PATCH v2 04/10] nfsd: Distinguish between required and optional NFSv3 post-op attributes Chuck Lever III
2021-12-19 21:09 ` Trond Myklebust
2021-12-20 16:02 ` Chuck Lever III
2021-12-20 18:38 ` Trond Myklebust
2021-12-20 19:22 ` Chuck Lever III
2021-12-21 18:10 ` [PATCH v2 00/10] Assorted patches for knfsd Chuck Lever III
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=3167a9a815ac9c82700bd58d8c421de31eee8b91.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=bfields@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@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