From owner-freebsd-current@FreeBSD.ORG Sat Oct 25 22:02:01 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 42BAD804 for ; Sat, 25 Oct 2014 22:02:01 +0000 (UTC) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 09EE3F67 for ; Sat, 25 Oct 2014 22:02:00 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArQEAPAcTFSDaFve/2dsb2JhbABcg2JYBIMCykYMhndUAoEbAX2EAgEBAQMBAQEBICsgCwUWGAICDRkCKQEJJgYIBwQBHASICwMJCQ2zdI1yF4YuAQEBAQEBBAEBAQEBAQEbgSyPCwEBGzQHgjZBEoFCBZZPhA6EcZRBhBQhLwEBAQSBCDmBAwEBAQ X-IronPort-AV: E=Sophos;i="5.04,788,1406606400"; d="scan'208";a="163513860" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-annu.net.uoguelph.ca with ESMTP; 25 Oct 2014 18:01:58 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 9E415AE931; Sat, 25 Oct 2014 18:01:58 -0400 (EDT) Date: Sat, 25 Oct 2014 18:01:58 -0400 (EDT) From: Rick Macklem To: Beeblebrox Message-ID: <1906655738.7488451.1414274518637.JavaMail.root@uoguelph.ca> In-Reply-To: <1414231671692-5959433.post@n5.nabble.com> Subject: Re: Some NFS server V4 questions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.201] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) Cc: freebsd-current@freebsd.org 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 22:02:01 -0000 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@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" >