Date: Fri, 11 Dec 2020 23:06:27 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: mike tancsa <mike@sentex.net>, J David <j.david.lists@gmail.com>, "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: Re: forcing nfsv4 versions from the server? (was Re: Major issues with nfsv4 Message-ID: <YQXPR0101MB096887867B39EB38AA171357DDCA0@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <318cbeaf-ce39-6ed7-3c64-8dc0efc540ce@sentex.net> References: <CABXB=RRB2nUk0pPDisBQPdicUA3ooHpg8QvBwjG_nFU4cHvCYw@mail.gmail.com> <YQXPR0101MB096849ADF24051F7479E565CDDCA0@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM>, <318cbeaf-ce39-6ed7-3c64-8dc0efc540ce@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
mike tancsa wrote:=0A=
[stuff snipped]=0A=
>Hi Rick,=0A=
>=0A=
> I never knew there was such an important difference. Is there a way=0A=
>on the server side to force only v4.1 connections from the client when=0A=
>they try and v4.x mount ?=0A=
You can set the sysctl:=0A=
vfs.nfsd.server_min_minorversion4=3D1=0A=
if your server has it. (I can't remember what versions of FreeBSD have it.)=
=0A=
=0A=
For Linux clients, they will usually use the highest minor version the=0A=
server supports. FreeBSD clients will use 0 unless the "minorversion=3D1"=
=0A=
option is on the mount command.=0A=
=0A=
To be honest, I have only heard of a couple of other sites having the=0A=
NFSERR_BADSEQID (10026) error problem and it sounds like J David's=0A=
problem is related to nullfs and jails.=0A=
=0A=
4.0->4.1 was a minor revision in name only. RFC5661 (the NFSv4.1 one)=0A=
is over 500pages. Not a trivial update. On the other hand, 4.1->4.2 is=0A=
a minor update, made up of a bunch of additional optional features=0A=
like SEEK_HOLE/SEEK_DATA support and local copy_file_range() support=0A=
in the server.=0A=
=0A=
rick=0A=
=0A=
=0A=
---Mike=0A=
=0A=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YQXPR0101MB096887867B39EB38AA171357DDCA0>