Date: Fri, 11 Dec 2020 11:33:22 -0500 From: mike tancsa <mike@sentex.net> To: Rick Macklem <rmacklem@uoguelph.ca>, J David <j.david.lists@gmail.com>, "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: forcing nfsv4 versions from the server? (was Re: Major issues with nfsv4 Message-ID: <318cbeaf-ce39-6ed7-3c64-8dc0efc540ce@sentex.net> In-Reply-To: <YQXPR0101MB096849ADF24051F7479E565CDDCA0@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM> References: <CABXB=RRB2nUk0pPDisBQPdicUA3ooHpg8QvBwjG_nFU4cHvCYw@mail.gmail.com> <YQXPR0101MB096849ADF24051F7479E565CDDCA0@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
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 ? ---Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?318cbeaf-ce39-6ed7-3c64-8dc0efc540ce>