Date: Sun, 26 Oct 2014 11:11:00 -0700 (PDT) From: Beeblebrox <zaphod@berentweb.com> To: freebsd-current@freebsd.org Subject: Re: Some NFS server V4 questions Message-ID: <20141026201045.04af8c34@rsbsd.rsb> In-Reply-To: <704800695.7624925.1414325968854.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> <20141026104814.6f72435c@rsbsd.rsb> <704800695.7624925.1414325968854.JavaMail.root@uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Dan: >> to get pxeboot to do v3, add to /boot/loader.conf >> boot-nfsroot-options=“nfsv3” Thanks. I'm using grub for the bootloader and menu, and comparable entry should be: set kfreebsd.boot.nfsroot.options="nfsv3" It does not work however. mount_root hangs for a while then reverts to V2. I've asked about this on the grub-devel list, and will share the answer here. Rick: Would it be worth trying to pass a nolockd option for this? As you had stated in another thread, "For NFSv3 mounts, I'd suggest the nolockd option, unless you have multiple clients concurrently doing byte range locking on the same file. (With "nolockd" option on the mounts, you shouldn't need to run rpc.lockd, rpc.statd and that implies NFSLOCKD shouldn't be needed, too.)" Should I try this? If yes, how is it done? >> Just fyi, "hard" is the default and "intr" is an alternative to "hard", so I'm not sure what you get when specifying both? You should choose one or the other. (You will get "hard" for the first 2 entries.) Thanks. Corrected by removing both. Konstantin: Have not gotten around to trying the code yet and thanks. ----- FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/Some-NFS-server-V4-questions-tp5959433p5959686.html Sent from the freebsd-current mailing list archive at Nabble.com. From owner-freebsd-current@FreeBSD.ORG Sun Oct 26 20:30:28 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 AAE0AA4B for <freebsd-current@freebsd.org>; Sun, 26 Oct 2014 20:30:28 +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 72403200 for <freebsd-current@freebsd.org>; Sun, 26 Oct 2014 20:30:27 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aq0EACNZTVSDaFve/2dsb2JhbABcg2JYBIMCyWYMhndUAoEeAX2EAgEBAQMBAQEBICsgCxsYAgINGQIpAQkmBggHBAEcBIgLAwkJDbNQjS8Xhi4BAQEHAQEBAQEBARuBLI8LAQEbATMHgneBVAWWT4QOhHGUQYQUIS8BAQEEgQg5gQMBAQE X-IronPort-AV: E=Sophos;i="5.04,791,1406606400"; d="scan'208";a="163612419" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-annu.net.uoguelph.ca with ESMTP; 26 Oct 2014 16:30:25 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id D2748B404E; Sun, 26 Oct 2014 16:30:25 -0400 (EDT) Date: Sun, 26 Oct 2014 16:30:25 -0400 (EDT) From: Rick Macklem <rmacklem@uoguelph.ca> To: Beeblebrox <zaphod@berentweb.com> Message-ID: <1453060363.7814476.1414355425851.JavaMail.root@uoguelph.ca> In-Reply-To: <20141026201045.04af8c34@rsbsd.rsb> Subject: Re: Some NFS server V4 questions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Originating-IP: [172.17.91.202] 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 <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 20:30:28 -0000 Beeblebrox wrote: > Dan: > >> to get pxeboot to do v3, add to /boot/loader.conf > >> boot-nfsroot-options=“nfsv3” > Thanks. I'm using grub for the bootloader and menu, and comparable > entry should be: > set kfreebsd.boot.nfsroot.options="nfsv3" > It does not work however. mount_root hangs for a while then reverts > to V2. I've asked about this on the grub-devel list, and will share > the answer here. > > Rick: > Would it be worth trying to pass a nolockd option for this? As you > had stated in another thread, > "For NFSv3 mounts, I'd suggest the nolockd option, unless you have > multiple clients concurrently doing byte range locking on the same > file. (With "nolockd" option on the mounts, you shouldn't need to > run rpc.lockd, rpc.statd and that implies NFSLOCKD shouldn't be > needed, too.)" > Should I try this? If yes, how is it done? > Well, I thought that the root fs was remounted ("mount -u") using the options specified in /etc/fstab for the root fs. As far as I know, putting the "nolockd" option there should work. rick > >> Just fyi, "hard" is the default and "intr" is an alternative to > >> "hard", so I'm not sure what you get when specifying both? You > >> should choose one or the other. (You will get "hard" for the > >> first 2 entries.) > Thanks. Corrected by removing both. > > Konstantin: > Have not gotten around to trying the code yet and thanks. > > > > > ----- > FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS > -- > View this message in context: > http://freebsd.1045724.n5.nabble.com/Some-NFS-server-V4-questions-tp5959433p5959686.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?20141026201045.04af8c34>