Date: Tue, 21 Mar 2017 09:13:39 +0100 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Daniel Braniss <danny@cs.huji.ac.il> Cc: Toomas Soome <tsoome@me.com>, Rick Macklem <rmacklem@uoguelph.ca>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: NFSv2 boot & OLD_NFSV2 Message-ID: <20170321081339.2wbx3rb32qdavvn3@ivaldir.net> In-Reply-To: <84D239AB-AB57-4A50-9700-E42BBF9CBE5A@cs.huji.ac.il> References: <38DD1950-AD12-4A27-8335-54F997E408DF@me.com> <20170320192000.6hal22ibnr3ajog3@ivaldir.net> <YTXPR01MB0189B266270E22DADF9A48EADD3A0@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM> <1B7471CD-2F2D-4F22-9D25-E46580CF9E96@me.com> <84D239AB-AB57-4A50-9700-E42BBF9CBE5A@cs.huji.ac.il>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Tue, Mar 21, 2017 at 09:58:21AM +0200, Daniel Braniss wrote: > > > On 20 Mar 2017, at 23:55, Toomas Soome <tsoome@me.com> wrote: > > > >> > >> On 20. märts 2017, at 23:53, Rick Macklem <rmacklem@uoguelph.ca> wrote: > >> > >> Baptiste Daroussin wrote: > >>> On Mon, Mar 20, 2017 at 08:22:12PM +0200, Toomas Soome wrote: > >>>> Hi! > >>>> > >>>> The current boot code is building NFSv3, with preprocessor conditional OLD_NFSV2. Should NFSv2 code still be kept around or can we burn it? > >>>> > >>>> rgds, > >>>> toomas > >>> > >>> I vote burn > >>> > >>> 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. > >> > >> Does booting over NFSv3 affect this? > >> > >> 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). > >> > >> 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.) > >> > >> rick > > > > if they do not suspect, they most likely use v3 - due to simple fact that you have to rebuild loader to use NFSv2 - it is compile time option. > > > > 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 to use FreeBSD server and the day was > saved. So, till these machines get upgraded/discontinued we have a problem. There are several solutions > to this issue, but as long as it's a matter of getting rid for the sake of it, I would vote to keep it a while longer. > > danny > > 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 said by Toomas that is it is already off by default in the 12.0 loader) am I missing something? Best regards, Bapt [-- Attachment #2 --] -----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-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170321081339.2wbx3rb32qdavvn3>