From: Peter Staubach <staubach@redhat.com>
To: Bill Johnstone <beejstone3@yahoo.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Configuration for NFSv3 only?
Date: Mon, 25 Jul 2005 17:47:37 -0400 [thread overview]
Message-ID: <42E55DF9.50609@redhat.com> (raw)
In-Reply-To: <20050725204047.82740.qmail@web33907.mail.mud.yahoo.com>
Bill Johnstone wrote:
>Hello all.
>
>What I would like to do is configure my server and clients to use NFSv3
>only. I'm running recent 2.6 kernels, e.g. 2.6.12 . I have read the
>FAQ on nfs.sourceforge.net .
>
>My kernel on the server is configured for Providing NFS3 client and
>server support. My kernel on the test client is configured for NFS3
>client support.
>
>My init script on the server is giving rpc.mountd the "-N 1 -N 2"
>command-line options.
>
>Running "rpcinfo -p" on the server gives:
>
> 100000 2 tcp 111 portmapper
> 100000 2 udp 111 portmapper
> 100024 1 udp 32768 status
> 100024 1 tcp 32769 status
> 100003 2 udp 2049 nfs
> 100003 3 udp 2049 nfs
> 100003 2 tcp 2049 nfs
> 100003 3 tcp 2049 nfs
> 100021 1 udp 32770 nlockmgr
> 100021 3 udp 32770 nlockmgr
> 100021 4 udp 32770 nlockmgr
> 100021 1 tcp 32770 nlockmgr
> 100021 3 tcp 32770 nlockmgr
> 100021 4 tcp 32770 nlockmgr
> 100005 3 udp 687 mountd
> 100005 3 tcp 690 mountd
>
>On the client, trying to perform a "mount -o vers=3 <server
>IP>:<exportname> <local mountpoint>" gives the error "NFSv3 not
>supported!" and the mount fails. If I remove the options to
>rpc.mountd, and do not specify "-o vers=3" on the client side, then
>mountd listens for protocol versions 1 and 2, and the mount succeeds.
>
>This leads me to the following questions:
>
>1. Should "rpcinfo -p" list a version 3 for portmapper in order for
>NFSv3 to be successfully used, or should portmapper only be at version
>2 even for the NFSv3 protocol?
>
The answer to this question is that the portmapper protocol is completely
separate from the NFS and related protocols such as nlockmgr and mountd.
There are newer versions of the protocol, 10000, which are now called
rpcbind.
But, the short answer, is that portmapper, version 2, is fine for these
purposes.
Thanx...
ps
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-07-25 21:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 20:40 Configuration for NFSv3 only? Bill Johnstone
2005-07-25 20:51 ` Trond Myklebust
2005-07-25 21:17 ` Bill Johnstone
2005-07-25 21:27 ` Trond Myklebust
2005-07-25 22:30 ` Bill Johnstone
2005-07-25 23:38 ` Trond Myklebust
2005-07-26 3:55 ` Bill Johnstone
2005-07-26 15:25 ` Trond Myklebust
2005-07-26 22:52 ` Bill Johnstone
2005-07-27 0:32 ` Trond Myklebust
2005-07-25 22:32 ` Bill Johnstone
2005-07-25 21:47 ` Peter Staubach [this message]
2005-07-25 22:35 ` Bill Johnstone
2005-07-26 12:52 ` Peter Staubach
2005-07-26 22:48 ` Bill Johnstone
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=42E55DF9.50609@redhat.com \
--to=staubach@redhat.com \
--cc=beejstone3@yahoo.com \
--cc=nfs@lists.sourceforge.net \
/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.