From: Steve Dickson <SteveD@redhat.com>
To: ShaunR <mailinglists@unix-scripts.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFSv4 and portmap
Date: Tue, 26 Oct 2010 16:09:33 -0400 [thread overview]
Message-ID: <4CC7357D.8090106@RedHat.com> (raw)
In-Reply-To: <ia761h$921$1@dough.gmane.org>
On 10/26/2010 02:18 PM, ShaunR wrote:
> Everything i keep reading tells me that NFS4 does not need portmap but
> for some reason on the NFS server ( CentOS 5.x ) i cannot get the nfs
> services started unless portmap is running first.
>
> On the server i modified /etc/sysconfig/nfs with the following options
> MOUNTD_NFS_V1="no"
> MOUNTD_NFS_V2="no"
> RPCNFSDARGS="-N 2 -N 3 -U"
>
> For some reason if i uncomment MOUNTD_NFS_v3="no" i get errors.
>
> On the client, again a CentOS 5.x machine but with a newer custom built
> kernel, If i do not start portmap then when i run mount it takes about 2
> minutes for the filesystem to mount and i see the following messages in
> /var/log/messages
>
> Oct 26 10:25:30 host kernel: rpcbind: server localhost not responding,
> timed out
>
> If i start portmap, the mount command completed in a few seconds.
>
>
> My goal here to is run/support NFSv4 Only.
I think you are running into a known problem of when the v4
server comes it uses some legacy code that blindly does
"unregister all my previous existences" to rpcbind.
So that unregister hangs for a bit if rpcbind is not
running... This was fixed in later releases...
steved.
prev parent reply other threads:[~2010-10-26 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 18:18 NFSv4 and portmap ShaunR
2010-10-26 20:09 ` 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=4CC7357D.8090106@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=mailinglists@unix-scripts.com \
/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.