Date: Sun, 26 Oct 2014 01:48:19 -0700 (PDT) From: Beeblebrox <zaphod@berentweb.com> To: freebsd-current@freebsd.org Subject: Re: Some NFS server V4 questions Message-ID: <20141026104814.6f72435c@rsbsd.rsb> In-Reply-To: <1792153082.7496945.1414276866911.JavaMail.root@uoguelph.ca> References: <1414231671692-5959433.post@n5.nabble.com> <544BC6B7.90608@pinyon.org> <20141025195819.1cc75873@rsbsd.rsb> <544C084A.3070807@pinyon.org> <1792153082.7496945.1414276866911.JavaMail.root@uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Sorry guys, we have a considerable time-zone difference. >> It appears that the sysctl must be set before mountd, nfsd are >> started to take effect. (Or they must be restarted after it is set.) I had apparently re-started nfsd but not mountd. This time re-starting both and launching the PXE client fails at mount_root stage as expected: exec /sbin/init: error 43 exec /rescue/init: error 43 panic: no init One cannot set "sysctl vfs.nfsd.server_min_nfsvers=4" until one of mountd/nfsd is started however, otherwise it gives an error. I have not tried, but I suppose this error does not happen when placeed in /etc/sysctl.conf? sysctl: unknown oid 'vfs.nfsd.server_min_nfsvers': No such file or directory >> Maybe it was the talk about getting rid of the oldnfs stuff that >> made you think V2, 3 were going away? Yes, that was it and I obviously misunderstood that thread. What's the max NFS version that supports mount_root from PXE clients then? As I recall, this would be V3. However, root is consistently being mounted as V2. The fstab for diskless clients: 192.168.2.1:/data/amd64 / nfs ro,nfsv3 0 0 192.168.2.1:/usr/local /usr/local nfs ro,nfsv4 0 0 192.168.2.1:/home /home nfs rw,nfsv4,hard,intr 0 0 nfsstat shows "/" as NFSV2, while the other two are NFSV4. Changing fstab entry to nfsv4 for root gives same result. I tried set "sysctl vfs.nfsd.server_min_nfsvers=3" and I get the same mount_root error as when this was set to 4. Im I missing something? It does not seem that "vfs.nfsd.server_min_nfsvers" will be of much use to me, unless I can get > V2 to mount as root. 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-tp5959433p5959595.html Sent from the freebsd-current mailing list archive at Nabble.com. From owner-freebsd-current@FreeBSD.ORG Sun Oct 26 09:38:05 2014 Return-Path: <owner-freebsd-current@FreeBSD.ORG> 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 CBCC46FD for <freebsd-current@freebsd.org>; Sun, 26 Oct 2014 09:38:05 +0000 (UTC) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7C9711AA for <freebsd-current@freebsd.org>; Sun, 26 Oct 2014 09:38:04 +0000 (UTC) Received: from th-04.cs.huji.ac.il ([132.65.80.125]) by kabab.cs.huji.ac.il with esmtp id 1XiKAt-000KR3-Qq; Sun, 26 Oct 2014 11:31:47 +0200 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) Subject: Re: Some NFS server V4 questions From: Daniel Braniss <danny@cs.huji.ac.il> In-Reply-To: <20141026104814.6f72435c@rsbsd.rsb> Date: Sun, 26 Oct 2014 11:31:46 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <C7E1AEF6-07A1-44D8-A412-1EBE005EBE7B@cs.huji.ac.il> References: <1414231671692-5959433.post@n5.nabble.com> <544BC6B7.90608@pinyon.org> <20141025195819.1cc75873@rsbsd.rsb> <544C084A.3070807@pinyon.org> <1792153082.7496945.1414276866911.JavaMail.root@uoguelph.ca> <20141026104814.6f72435c@rsbsd.rsb> To: Beeblebrox <zaphod@berentweb.com> X-Mailer: Apple Mail (2.1990.1) 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 <freebsd-current.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>; List-Post: <mailto:freebsd-current@freebsd.org> List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, <mailto:freebsd-current-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sun, 26 Oct 2014 09:38:05 -0000 > On Oct 26, 2014, at 10:48 AM, Beeblebrox <zaphod@berentweb.com> wrote: >=20 > Sorry guys, we have a considerable time-zone difference. >=20 >>> It appears that the sysctl must be set before mountd, nfsd are >>> started to take effect. (Or they must be restarted after it is set.) > I had apparently re-started nfsd but not mountd. This time re-starting = both and launching the PXE client fails at mount_root stage as expected: > exec /sbin/init: error 43 > exec /rescue/init: error 43 > panic: no init >=20 > One cannot set "sysctl vfs.nfsd.server_min_nfsvers=3D4" until one of = mountd/nfsd is started however, otherwise it gives an error. I have not = tried, but I suppose this error does not happen when placeed in = /etc/sysctl.conf? > sysctl: unknown oid 'vfs.nfsd.server_min_nfsvers': No such file or = directory >=20 >>> Maybe it was the talk about getting rid of the oldnfs stuff that >>> made you think V2, 3 were going away? > Yes, that was it and I obviously misunderstood that thread. >=20 > What's the max NFS version that supports mount_root from PXE clients = then? As I recall, this would be V3. However, root is consistently being = mounted as V2. to get pxeboot to do v3, add: boot-nfsroot-options=3D=E2=80=9Cnfsv3=E2=80=9D to /boot/loader.conf > The fstab for diskless clients: > 192.168.2.1:/data/amd64 / nfs ro,nfsv3 0 0 > 192.168.2.1:/usr/local /usr/local nfs ro,nfsv4 0 0 > 192.168.2.1:/home /home nfs rw,nfsv4,hard,intr 0 0 >=20 > nfsstat shows "/" as NFSV2, while the other two are NFSV4. Changing = fstab entry to nfsv4 for root gives same result. > I tried set "sysctl vfs.nfsd.server_min_nfsvers=3D3" and I get the = same mount_root error as when this was set to 4. Im I missing something? = It does not seem that "vfs.nfsd.server_min_nfsvers" will be of much use = to me, unless I can get > V2 to mount as root. >=20 > Regards. >=20 >=20 >=20 >=20 > ----- > FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS > -- > View this message in context: = http://freebsd.1045724.n5.nabble.com/Some-NFS-server-V4-questions-tp595943= 3p5959595.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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141026104814.6f72435c>