From: "J. Bruce Fields" <bfields@fieldses.org>
To: Gareth Williams <gareth@garethwilliams.me.uk>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Question ref Running NFS at V4 Only
Date: Mon, 23 Dec 2013 12:39:56 -0500 [thread overview]
Message-ID: <20131223173956.GA9221@fieldses.org> (raw)
In-Reply-To: <52B47A12.2070202@garethwilliams.me.uk>
On Fri, Dec 20, 2013 at 05:10:42PM +0000, Gareth Williams wrote:
> Hi,
>
> I'm trying to run NFS with protocol version 4 only (that is, with v2
> & v3 disabled) on a CentOS 6.5 install running as a KVM guest.
>
> The RedHat documentation (amongst others) states that rpcbind isn't
> needed with v4, but if I start nfs without rpcbind I get errors.
I suspect the kernel code needs to be fixed to not attempt to register
with rpcbind n the v4-only case. (Or to attempt to register but ignore
any error, I'm not sure which is best.)
And this may not be the only issue in the v4-only case. This isn't
really a priority for me right now, but I'd happily look at patches.
--b.
>
> I've spent a couple of days (on and off) on Google trying to get an
> answer and have posted on the CentOS forum, but the nearest I can
> find is an archive on this mailing list from over two years ago
> (and it's not identical):-
>
> http://www.spinics.net/lists/linux-nfs/msg16907.html
>
> In /etc/sysconfig/nfs I have:-
>
> MOUNTD_NFS_V2="no"
> MOUNTD_NFS_V3="no"
>
> RPCNFSDARGS="-N 2 -N 3"
>
> When I attempt to start NFS either using the init scripts or
> manually with:-
>
> rpc.nfsd -N 2 -N 3
>
> I get:-
>
> rpc.nfsd: writing fd to kernel failed: errno 111 (Connection refused)
> rpc.nfsd: unable to set any sockets for nfsd
>
> The mailing list archive's answer was that the kernel was too old,
> so I installed 3.10.24 from elrepo but the symptom doesn't change.
>
> If I start rpcbind, then everything works, but as far as I can see,
> I shouldn't have to do that unless I'm supporting v2 & v3.
>
> Finally, please accept my apologies for wasting your time if I've
> missed something obvious.
>
> Kind regards,
>
> Gareth
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-12-23 17:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 17:10 Question ref Running NFS at V4 Only Gareth Williams
2013-12-23 17:39 ` J. Bruce Fields [this message]
2013-12-27 10:17 ` Kinglong Mee
2013-12-27 16:05 ` Chuck Lever
2013-12-27 18:43 ` J.;Bruce Fields
2013-12-27 19:40 ` Chuck Lever
[not found] ` <6E281EC9-49CB-4BDA-BDF3-7A6F4B703156@gmail.com>
2013-12-29 6:39 ` Kinglong Mee
[not found] ` <5D65FDE6-D1AB-442C-BFD8-141AB87FF321@gmail.com>
2013-12-29 9:11 ` Kinglong Mee
2013-12-30 11:22 ` Kinglong Mee
2013-12-30 11:24 ` [PATCH 1/2] SUNRPC: supports ignoring error from svc_register Kinglong Mee
2013-12-30 11:25 ` [PATCH 2/2] NFSD: supports nfsv4 service without rpcbind Kinglong Mee
2013-12-30 17:54 ` Chuck Lever
2013-12-31 3:18 ` Kinglong Mee
2013-12-31 5:17 ` [PATCH 1/2 v2] SUNRPC/NFSD: Supports new option for ignoring the result of svc_register Kinglong Mee
2013-12-31 5:17 ` [PATCH 2/2 v2] NFSD: Don't start lockd when only NFSv4 is running Kinglong Mee
2014-01-03 23:18 ` J.,Bruce Fields
2014-01-06 3:28 ` NFSD: fix compile warning without CONFIG_NFSD_V3 Kinglong Mee
2014-01-06 18:44 ` J.,Bruce Fields
2013-12-31 19:39 ` [PATCH 1/4] SUNRPC: Ensure xprt_connect_status handles all potential connection errors Trond Myklebust
2013-12-31 19:39 ` [PATCH 2/4] SUNRPC: Handle connect errors ECONNABORTED and EHOSTUNREACH Trond Myklebust
2013-12-31 19:39 ` [PATCH 3/4] SUNRPC: Report connection error values to rpc_tasks on the pending queue Trond Myklebust
2013-12-31 19:39 ` [PATCH 4/4] SUNRPC: Add tracepoint for socket errors Trond Myklebust
2014-01-05 19:54 ` J. Bruce Fields
2014-01-05 20:19 ` Trond Myklebust
2014-01-02 4:52 ` [PATCH 1/4] SUNRPC: Ensure xprt_connect_status handles all potential connection errors Kinglong Mee
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=20131223173956.GA9221@fieldses.org \
--to=bfields@fieldses.org \
--cc=gareth@garethwilliams.me.uk \
--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.