From owner-freebsd-current@freebsd.org Tue Mar 21 08:01:42 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD089D16231 for ; Tue, 21 Mar 2017 08:01:42 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (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 0C3F6A43; Tue, 21 Mar 2017 08:01:42 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from bach.cs.huji.ac.il ([132.65.80.20]) by kabab.cs.huji.ac.il with esmtp id 1cqEja-000MWN-P2; Tue, 21 Mar 2017 10:01:38 +0200 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: NFSv2 boot & OLD_NFSV2 From: Daniel Braniss In-Reply-To: Date: Tue, 21 Mar 2017 10:01:38 +0200 Cc: Baptiste Daroussin , Toomas Soome , FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: <3429CB2E-AAF1-47C2-B1B2-400A3819C7FB@cs.huji.ac.il> References: <38DD1950-AD12-4A27-8335-54F997E408DF@me.com> <20170320192000.6hal22ibnr3ajog3@ivaldir.net> To: Rick Macklem X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Tue, 21 Mar 2017 08:01:42 -0000 > On 20 Mar 2017, at 23:53, Rick Macklem wrote: >=20 > Baptiste Daroussin wrote: >> On Mon, Mar 20, 2017 at 08:22:12PM +0200, Toomas Soome wrote: >>> Hi! >>>=20 >>> The current boot code is building NFSv3, with preprocessor = conditional OLD_NFSV2. Should NFSv2 code still be kept around or can we = burn it? >>>=20 >>> rgds, >>> toomas >>=20 >> I vote burn >>=20 >> Bapt > I would be happy to see NFSv2 go away. However, depending on how = people configure > their diskless root fs, they do end up using NFSv2 for their root fs. >=20 > Does booting over NFSv3 affect this? >=20 > I think the answer is no for a FreeBSD server (since the NFSv2 File = Handle is the same as > the NFSv3 one, except padded with 0 bytes to 32bytes long). > However, there might be non-FreeBSD NFS servers where the NFSv2 file = handle is different > than the NFSv3 one and for that case, the user would need NFSv2 boot = code (or > reconfigure their root fs to use NFSv3). >=20 > To be honest, I suspect few realize that they are using NFSv2 for = their root fs. > (They'd see it in a packet trace or via "nfsstat -m", but otherwise = they probably > think they are using NFSv3 for their root fs.) this just what happened here, we upgraded our main NetApp, and few = machines started working funny, so we moved them to use FreeBSD instead and all was ok again.=20 danny >=20 > rick > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org"