Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 21 Mar 2017 10:01:38 +0200
From:      Daniel Braniss <danny@cs.huji.ac.il>
To:        Rick Macklem <rmacklem@uoguelph.ca>
Cc:        Baptiste Daroussin <bapt@FreeBSD.org>, Toomas Soome <tsoome@me.com>, FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: NFSv2 boot & OLD_NFSV2
Message-ID:  <3429CB2E-AAF1-47C2-B1B2-400A3819C7FB@cs.huji.ac.il>
In-Reply-To: <YTXPR01MB0189B266270E22DADF9A48EADD3A0@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM>
References:  <38DD1950-AD12-4A27-8335-54F997E408DF@me.com> <20170320192000.6hal22ibnr3ajog3@ivaldir.net> <YTXPR01MB0189B266270E22DADF9A48EADD3A0@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM>

next in thread | previous in thread | raw e-mail | index | archive | help

> On 20 Mar 2017, at 23:53, Rick Macklem <rmacklem@uoguelph.ca> 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"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3429CB2E-AAF1-47C2-B1B2-400A3819C7FB>