From owner-freebsd-fs@freebsd.org Wed May 12 06:40:26 2021 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 CDE7C633225 for ; Wed, 12 May 2021 06:40:26 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fg4t25XSgz3mhx; Wed, 12 May 2021 06:40:26 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from [192.168.0.88] (unknown [195.64.148.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: avg/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 5AB232B08E; Wed, 12 May 2021 06:40:26 +0000 (UTC) (envelope-from avg@FreeBSD.org) Subject: Re: Changes in vfs.zfs.arc_max on 13 To: Pete Wright , freebsd-fs@freebsd.org References: <0961dfe0-922e-8a6f-0bf9-c0685e3ec3d1@nomadlogic.org> From: Andriy Gapon Message-ID: Date: Wed, 12 May 2021 09:40:23 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Firefox/78.0 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: <0961dfe0-922e-8a6f-0bf9-c0685e3ec3d1@nomadlogic.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit 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: Wed, 12 May 2021 06:40:26 -0000 On 11/05/2021 20:09, Pete Wright via freebsd-fs wrote: > The next issue I am seeing is that when setting this variable the example from > the handbook states you can do something similar to this (section 20.6.2.3): > > vfs.zfs.arc_max="40M" > > This throws an error on my system: > $ sudo sysctl vfs.zfs.arc_max=2048M > sysctl: invalid unsigned long '2048M' > $ sudo sysctl vfs.zfs.arc_max=2G > sysctl: invalid unsigned long '2G' > > Using the human unfriendly form works though: > $ sudo sysctl vfs.zfs.arc.max="2000000000" > vfs.zfs.arc.max: 0 -> 2000000000 > $ > > Is this a bug, or would it be best to also update the documentation accordingly > to reflect this?  Personally I like the old behavior as it's easier on my eyes. Are you sure that that is a recipe for sysctl? It looks like it was for loader.conf. -- Andriy Gapon