forcing nfsv4 versions from the server? (was Re: Major issues with nfsv4

[Rick Macklem]

mike tancsa wrote:
[stuff snipped]
>Hi Rick,
>
>    I never knew there was such an important difference. Is there a way
>on the server side to force only v4.1 connections from the client when
>they try and v4.x mount ?
You can set the sysctl:
vfs.nfsd.server_min_minorversion4=1
if your server has it. (I can't remember what versions of FreeBSD have it.)

For Linux clients, they will usually use the highest minor version the
server supports. FreeBSD clients will use 0 unless the  "minorversion=1"
option is on the mount command.

To be honest, I have only heard of a couple of other sites having the
NFSERR_BADSEQID (10026) error problem and it sounds like J David's
problem is related to nullfs and jails.

4.0->4.1 was a minor revision in name only. RFC5661 (the NFSv4.1 one)
is over 500pages. Not a trivial update. On the other hand, 4.1->4.2 is
a minor update, made up of a bunch of additional optional features
like SEEK_HOLE/SEEK_DATA support and local copy_file_range() support
in the server.

rick


    ---Mike