can you (theoretically) run only NFSv4 (without earlier versions)?

Peter Skensved peter at jay.Phy.QueensU.CA
Tue Dec 24 02:34:25 UTC 2013


On 12/24/13 09:12, Robert P. J. Day wrote:
>   as a quick test, i added "-U" but the only change was that
> "rpcinfo -p" showed me that UDP was no longer being accepted
> for v4 only:
>
>     100003    3   tcp   2049  nfs
>     100227    3   tcp   2049  nfs_acl
>     100003    3   udp   2049  nfs
>     100227    3   udp   2049  nfs_acl
>     100003    4   tcp   2049  nfs
>
> to match what i see under RHEL, i was hoping to see *all*
> references to NFSv3 disappear from the output of that command.
> i'll test further later.

   For what it is worth CentOS6.4 reports something similar when
running rcpinfo -p on a server with this in /etc/sysconfig/nfs :

# Define which protocol versions mountd 
# will advertise. The values are "no" or "yes"
# with yes being the default
#MOUNTD_NFS_V1="no"
MOUNTD_NFS_V2="no"
MOUNTD_NFS_V3="no"
#

...

RPCNFSDARGS="-N 2 -N 3"


 However if I try to mount with -t nfs on a client I get a nfs4 type
mount ( same as with -t nfs4 ) . On the other hand if I ask for
a -t nfs -o nfsvers=3 mount it just hangs forever. Only tcp port
2049 is open in iptables although nmap -sU tells me that various
NFS related things are listening locally. 

 On the server itself an attempt to mount version 3 results in a :
mount.nfs: Interrupted system call
so I guess the extra ( local ) udp stuff doesn't actually do anything .

              peter



 

 


More information about the users mailing list