Date: Fri, 14 May 2021 14:44:49 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: Daniel Ebdrup Jensen <debdrup@FreeBSD.org>, "freebsd-current@FreeBSD.org" <freebsd-current@FreeBSD.org> Subject: Re: RFC: changing the default NFSv4 minor version? Message-ID: <YQXPR0101MB0968C3D984D44CD492C28818DD509@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <20210514082538.wbbrhhkwebvos6qc@nerd-thinkpad.local> References: <YQXPR0101MB096876462C2D45CB123431BCDD519 () YQXPR0101MB0968 ! CANPRD01 ! PROD ! OUTLOOK ! COM>,<20210514082538.wbbrhhkwebvos6qc@nerd-thinkpad.local>
next in thread | previous in thread | raw e-mail | index | archive | help
Daniel Ebdrup Jensen wrote:=0A= >On Thu, May 13, 2021 at 11:02:35PM +0000, Rick Macklem wrote:=0A= >>Hi,=0A= >>=0A= >>I believe that NFSv4.1 and NFSv4.2 are now mature in freebsd-current/main= .=0A= >>I also believe that NFSv4.1/4.2 is a better protocol than NFSv4.0.=0A= >>(In particular, the sessions mechanism for "exactly once RPC semantics"= =0A= >> is a significant improvement over the duplicate request cache for NFSv4.= 0,=0A= >> plus other improvements.)=0A= >>=0A= >>Right now, the FreeBSD NFSv4 client will use NFSv4.0 unless the=0A= >>"minorversion" mount option is used to set the minor version to 1 or 2.= =0A= >>=0A= >>The Linux client uses the highest minor version supported by both=0A= >>client and server by default.=0A= >>I'd like to propose that the default behaviour of the FreeBSD client=0A= >>be changed to do the same, so that NFSv4.1/4.2 will be used when possible= .=0A= >>--> The "minorversion" mount option could still be used to override the= =0A= >> above default.=0A= >>=0A= >>I have hesitated doing this change because it could be considered a POLA= =0A= >>violation, but I think the change from 4.0->4.1/4.2 will normally be a=0A= >>neutral to positive experience. (To be honest, I suspect most won't notic= e=0A= >>the change.)=0A= >>=0A= >>How do others feel about this change?=0A= >>=0A= >>rick=0A= >>_______________________________________________=0A= >>freebsd-current@freebsd.org mailing list=0A= >>https://lists.freebsd.org/mailman/listinfo/freebsd-current=0A= >>To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= =0A= >=0A= >Hi Rick,=0A= >=0A= > If I understand your plans correctly, you're not going to be making= =0A= > it so that minorversion=3DN complains?=0A= If by "complains" you mean "mount fails if the minor version is not support= ed=0A= by the server" then, yes, I am not planning on changing that.=0A= =0A= > In that case, I don't quite understand how it can be a POLA=0A= > violation, since presumably it'll fall back to NFSv4.0 if that's=0A= > the only thing that's supported by ntpd on some other system.=0A= The POLA violation is that, now, a mount without "minorversion" always=0A= uses NFSv4.0 and fails to mount if the server does not support NFSv4.0.=0A= =0A= > At any rate, I'm all for it since I'm already using NFSv4.2. :)=0A= Thanks for the input, rick=0A= =0A= Yours,=0A= Daniel Ebdrup Jensen=0A=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YQXPR0101MB0968C3D984D44CD492C28818DD509>