From owner-freebsd-current@freebsd.org Tue Mar 21 08:13:41 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 24954D16630 for ; Tue, 21 Mar 2017 08:13:41 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D897D1410; Tue, 21 Mar 2017 08:13:40 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id 2B9097319; Tue, 21 Mar 2017 08:13:40 +0000 (UTC) Date: Tue, 21 Mar 2017 09:13:39 +0100 From: Baptiste Daroussin To: Daniel Braniss Cc: Toomas Soome , Rick Macklem , FreeBSD Current Subject: Re: NFSv2 boot & OLD_NFSV2 Message-ID: <20170321081339.2wbx3rb32qdavvn3@ivaldir.net> References: <38DD1950-AD12-4A27-8335-54F997E408DF@me.com> <20170320192000.6hal22ibnr3ajog3@ivaldir.net> <1B7471CD-2F2D-4F22-9D25-E46580CF9E96@me.com> <84D239AB-AB57-4A50-9700-E42BBF9CBE5A@cs.huji.ac.il> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="jr2dkby6gacluzxz" Content-Disposition: inline In-Reply-To: <84D239AB-AB57-4A50-9700-E42BBF9CBE5A@cs.huji.ac.il> User-Agent: NeoMutt/20170306 (1.8.0) 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:13:41 -0000 --jr2dkby6gacluzxz Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 21, 2017 at 09:58:21AM +0200, Daniel Braniss wrote: >=20 > > On 20 Mar 2017, at 23:55, Toomas Soome wrote: > >=20 > >>=20 > >> On 20. m=E4rts 2017, at 23:53, Rick Macklem wro= te: > >>=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 condition= al 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 peopl= e 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 Ha= ndle 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 h= andle is different > >> than the NFSv3 one and for that case, the user would need NFSv2 boot c= ode (or > >> reconfigure their root fs to use NFSv3). > >>=20 > >> To be honest, I suspect few realize that they are using NFSv2 for thei= r root fs. > >> (They'd see it in a packet trace or via "nfsstat -m", but otherwise th= ey probably > >> think they are using NFSv3 for their root fs.) > >>=20 > >> rick > >=20 > > if they do not suspect, they most likely use v3 - due to simple fact th= at you have to rebuild loader to use NFSv2 - it is compile time option. > >=20 >=20 > old systems, 8.x, still use/boot v2, and so do old linux. > NetApp has discontinued support for v2, so we had to move this machines t= o use FreeBSD server and the day was > saved. So, till these machines get upgraded/discontinued we have a proble= m. There are several solutions > to this issue, but as long as it's a matter of getting rid for the sake o= f it, I would vote to keep it a while longer. >=20 > danny >=20 >=20 Given you are speaking of 8.x I suppose you are using the loader that comes= with it, meaning you are safe if we remove it from the loader in 12.0 (note as s= aid by Toomas that is it is already off by default in the 12.0 loader) am I mis= sing something? Best regards, Bapt --jr2dkby6gacluzxz Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAljQ4LEACgkQY4mL3PG3 PlonNBAAru0NFlMmWVL/sjemOgzwm3rc0tarbB1wJTDt6fGuyIgGIMp7ZOVdl7wN ZR0KhfVhdpxcLXjBt36QqNQ/V6WTXUMyrQyRP0C2mUpWab/fc49hMbx25Lb7P1aB CHWXjV0+fbeDcK6Tq+1cAmm0fZM8yBzgOShW3m7tBO5O5UtyVIWVvRRJFdSOoTXw 0C7lw6zaxaY4R1/qGAKKLtEvEgTocdtMWOErIxFCjXSo+QerSGZbjBve6etbbtr5 Maw2YOXC6i/Xp596njGJhqg9izGzE2OUxUqkyQ51s4SR766n4brK77LFe5f4+sG+ HOAfmUDDxyMDNwBG34yhfzm0UxQfmBZXzJGA7OPn2GrkX2IB24za8XrCEQoYjJiw LV7xGbLVogZ/Ye21hVGuJODmgWMlb1yEgvKuQFSSjIGnaBJtzSFjquR1i1WXvEfg UN50pU2V5hHxjN4QsXA6fRUqwk2faEUOIUZxOPKYnBCmapbMCh2WCiePzBAt1In6 UemhrDerSLelnDVFHO02dtpkOwI1SzmRHbXQpPZQuUckG2WKn93zkkln3dVl06TR 0hgKxf6mC6OgksBO3AkXmTVv9Q4zkcLExtVmNJyUqnsMJwG6g00GyU6qunyaeR+b oAIGd+90X9b1ddzbQYJzG7hWvE6tgcKxbLY4QB40BeyFbgdLgf0= =iGWJ -----END PGP SIGNATURE----- --jr2dkby6gacluzxz--