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

mike tancsa mike at
Fri Dec 11 16:33:24 UTC 2020

On 12/10/2020 7:59 PM, Rick Macklem wrote:
> J. David wrote:
>> Recently, we attempted to get with the 2000's and try switching from
>> NFSv3 to NFSv4 on our 12.2 servers.  This has not gone well.
>> Any system we switch to NFSv4 mounts is functionally unusable, pegged
>> at 100% system CPU usage, load average 70+, largely from nfscl threads
>> and client processes using NFS.
>> Dmesg shows NFS-related messages:
>> $ dmesg | fgrep -i nfs | sort | uniq -c | sort -n
>>   1 nfsv4 err=10010
>>   4 nfsv4 client/server protocol prob err=10026
>>  29 nfscl: never fnd open
> Add "minorversion=1" to your FreeBSD NFS client mount options
> and error 10026 should go away (and I suspect that the 10010 will
> go away too.

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 ?


More information about the freebsd-fs mailing list