From owner-freebsd-fs@freebsd.org Fri Dec 11 16:33:24 2020 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 28A554B43D0 for ; Fri, 11 Dec 2020 16:33:24 +0000 (UTC) (envelope-from mike@sentex.net) Received: from pyroxene2a.sentex.ca (pyroxene19.sentex.ca [IPv6:2607:f3e0:0:3::19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "pyroxene.sentex.ca", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CsxDM2wm7z4ZXh for ; Fri, 11 Dec 2020 16:33:23 +0000 (UTC) (envelope-from mike@sentex.net) Received: from [IPv6:2607:f3e0:0:4:28bd:e794:2a7c:a8d8] ([IPv6:2607:f3e0:0:4:28bd:e794:2a7c:a8d8]) by pyroxene2a.sentex.ca (8.15.2/8.15.2) with ESMTPS id 0BBGXMF2042714 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Fri, 11 Dec 2020 11:33:22 -0500 (EST) (envelope-from mike@sentex.net) Subject: forcing nfsv4 versions from the server? (was Re: Major issues with nfsv4 To: Rick Macklem , J David , "freebsd-fs@freebsd.org" References: From: mike tancsa Message-ID: <318cbeaf-ce39-6ed7-3c64-8dc0efc540ce@sentex.net> Date: Fri, 11 Dec 2020 11:33:22 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 4CsxDM2wm7z4ZXh X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of mike@sentex.net designates 2607:f3e0:0:3::19 as permitted sender) smtp.mailfrom=mike@sentex.net X-Spamd-Result: default: False [0.58 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f3e0::/32]; HFILTER_HELO_IP_A(1.00)[pyroxene2a.sentex.ca]; HFILTER_HELO_NORES_A_OR_MX(0.30)[pyroxene2a.sentex.ca]; NEURAL_HAM_SHORT(-0.42)[-0.421]; FREEMAIL_TO(0.00)[uoguelph.ca,gmail.com,freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f3e0:0:3::19:from]; ASN(0.00)[asn:11647, ipnet:2607:f3e0::/32, country:CA]; MID_RHS_MATCH_FROM(0.00)[]; SUBJECT_HAS_QUESTION(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FREEFALL_USER(0.00)[mike]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TAGGED_RCPT(0.00)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[sentex.net]; SPAMHAUS_ZRD(0.00)[2607:f3e0:0:3::19:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(1.00)[1.000]; R_DKIM_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-fs] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Dec 2020 16:33:24 -0000 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