Re: Some NFS server V4 questions

Beeblebrox wrote:
> * I can't get the NFS server to run V4 only. I have:
> sysctl vfs.nfsd.server_min_nfsvers=4
> 
Hmm. With this set the NFS server shouldn't accept V2, 3
RPCs. The mount will work, since that is done by the Mount
protocol (mountd), but the client should be saying "server
not responding..." whenever it tries to access the V2, 3
mounts. Not sure why NFSv3 is still working after this is set.
I'll try a quick test of it here.

> I start all NFS-related services manually (from script)
> #!/bin/sh
> rpcbind -s -h 192.168.2.1
> mountd -rnl -h 192.168.2.1
> nfsd -ut -n 4 -h 192.168.2.1
> nfsuserd
> 
> /etc/exports has:
> V4:  /     -network 192.168.2.0/26
> /data/amd64      /data/amd64/boot/s386    -ro -network 192.168.2.0/26
> /usr/local	-ro -maproot=0	-network 192.168.2.0/26
> /home		-network 192.168.2.0/26
> 
> Running "nfsstat -m" from a PXE client gives me:
> 192.168.2.1:/data/amd64 on /
> nfsv2,tcp,resvport,hard,cto,lockd,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=8192,wsize=8192,readdirsize=8192,readahead=1,wcommitsize=1997092,timeout=120,retrans=2
> 192.168.2.1:/home on /home
> nfsv3,tcp,resvport,hard,intr,cto,lockd,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=65536,wsize=65536,readdirsize=65536,readahead=1,wcommitsize=1997092,timeout=120,retrans=2
> 192.168.2.1:/usr/local on /usr/local
> nfsv3,tcp,resvport,hard,cto,lockd,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=65536,wsize=65536,readdirsize=65536,readahead=1,wcommitsize=1997092,timeout=120,retrans=2
> 
> The PXE-booted kernel is compiled with: nfscommon, nfssvc, nfs,
> nfscl,
> nfslock
> On server side, in addition to the above, these are loaded as
> modules:
> acl_nfs4.ko, nfsd.ko, nfslockd.ko
> 
> PXE client's /etc/rc.conf the only NFS-related entry is:
> nfs_client_enable="YES"
> 
> PXE client's /etc/fstab is:
> 92.168.2.1:/data/amd64 /       nfs     ro      0       0
> 192.168.2.1:/usr/local /usr/local nfs   ro      0       0
> 192.168.2.1:/home       /home   nfs     rw,hard,intr    0  0
> 
> 
> * Considering V2/V3 for NFS is getting dropped from code base, PXE
> clients
> used to need max V3 as root and could not mount_root with V4. Has
> this
> changed? If so, what services do the clients need to get V4 on root
> working
> (RO, no RW)?
> 
I am not aware of any plans to drop V2/V3. Although V2 isn't used much
any more V3 will be around for a long time to come, imho. (I'll probably
be long gone before V3 is.)

The new client and server support V2, 3 and 4. (Maybe it was the talk
about getting rid of the oldnfs stuff that made you think V2, 3 were
going away?

rick

> * There was a simple command to show from server-side what version of
> NFS
> the exports were running, but I seem to have lost that. Any clues?
> 
> * Have any of these services become capable of running from inside a
> jail
> environment? {rpcbind mountd nfsd nfsuserd} - it does not seem so,
> but just
> checking.
> 
> Thanks and Regards.
> 
> 
> 
> -----
> FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
> --
> View this message in context:
> http://freebsd.1045724.n5.nabble.com/Some-NFS-server-V4-questions-tp5959433.html
> Sent from the freebsd-current mailing list archive at Nabble.com.
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to
> "freebsd-current-unsubscribe_at_freebsd.org"
>