Date: Wed, 12 May 2021 09:40:23 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Pete Wright <pete@nomadlogic.org>, freebsd-fs@freebsd.org Subject: Re: Changes in vfs.zfs.arc_max on 13 Message-ID: <dcf63f50-5ea6-8524-37b3-577bda3ba06f@FreeBSD.org> In-Reply-To: <0961dfe0-922e-8a6f-0bf9-c0685e3ec3d1@nomadlogic.org> References: <0961dfe0-922e-8a6f-0bf9-c0685e3ec3d1@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?dcf63f50-5ea6-8524-37b3-577bda3ba06f>