From owner-freebsd-current@FreeBSD.ORG Sat Oct 25 10:07:59 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 73325D90 for ; Sat, 25 Oct 2014 10:07:59 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 57D54F13 for ; Sat, 25 Oct 2014 10:07:58 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1XhyGF-0002En-Mt for freebsd-current@freebsd.org; Sat, 25 Oct 2014 03:07:51 -0700 Date: Sat, 25 Oct 2014 03:07:51 -0700 (PDT) From: Beeblebrox To: freebsd-current@freebsd.org Message-ID: <1414231671692-5959433.post@n5.nabble.com> Subject: Some NFS server V4 questions MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Oct 2014 10:07:59 -0000 * I can't get the NFS server to run V4 only. I have: sysctl vfs.nfsd.server_min_nfsvers=4 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)? * 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.