Date: Fri, 8 Jul 2016 02:48:16 -0400 From: Nathan Bosley <nathan.bosley@gmail.com> To: Steven Hartland <killing@multiplay.co.uk> Cc: Eric van Gyzen <vangyzen@freebsd.org>, freebsd-current@freebsd.org Subject: Re: Setting sysctl vfs.zfs.arc_max failed: 22 Message-ID: <CAB%2BRvm5o_Xc3Ufyj1%2B3rN26cEbTwuQ_rpk1RDgi8HZ0c346JhA@mail.gmail.com> In-Reply-To: <0a21b4f9-3f82-5e3b-3624-cad1e79489a0@multiplay.co.uk> References: <ccdd6a5b-4771-6207-adb3-ce9a7960485c@FreeBSD.org> <975e5ae2-2090-94cd-49c0-eee9866ff02b@freebsd.org> <CAB%2BRvm7c97ionaM02UgTLNt-aqQJLZ8%2B5ZoFL9gHDhmmx=cCcg@mail.gmail.com> <e1fd9ae9-71de-ec0f-53d2-1c5d2f9ccc87@multiplay.co.uk> <145180d1-43c9-d894-9221-b210d641955d@freebsd.org> <CAB%2BRvm6OpDQMz4vE7d0D76wDuPjzh597UaDXjNfrHLP59st_ag@mail.gmail.com> <7255f240-8cf0-0a62-89be-2a0970b67063@freebsd.org> <CAB%2BRvm4V88ppSdFJ-DsUf6AKx6UC=hdbA_r4LjMdtwLCRa9pVw@mail.gmail.com> <CAB%2BRvm63pnLSx-fX8kiZp5Q%2BMB424xnAZeXRAr-de%2BEHiW1XCQ@mail.gmail.com> <4d83c12e-e9d9-b5a8-e6cb-733924d6fd7d@multiplay.co.uk> <fbfdea3b-abf3-13c8-9c45-5f732d2e3445@FreeBSD.org> <0a21b4f9-3f82-5e3b-3624-cad1e79489a0@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
I was just testing this a bit. I can now set max in loader.conf as expected. I did notice one thing that I thought was a bit strange though. As a reference, here are my defaults without any ARC tunables/sysctls: vfs.zfs.arc_meta_limit: 3903459328 vfs.zfs.arc_min: 1951729664 vfs.zfs.arc_max: 15613837312 If I put vfs.zfs.arc_max="8589934592" in loader.conf, the results are: vfs.zfs.arc_meta_limit: 2147483648 vfs.zfs.arc_min: 1073741824 vfs.zfs.arc_max: 8589934592 So meta_limit and min are also changed, which is reasonable. If I remove all of my ARC tunables in loader.conf, so that I have the default values after booting, and then use: # sysctl vfs.zfs.arc_max="8589934592" The result is: vfs.zfs.arc_meta_limit: 2147483648 vfs.zfs.arc_min: 1951729664 vfs.zfs.arc_max: 8589934592 Max was set as requested. meta_limit was set to max/4. But min is still at the default. In other words, if I use loader.conf to set max, then min and meta_limit are also recalculated. But if I use sysctl to set max, only meta_limit is recalculated; min remains at the default. I'm not sure if that's the intent. Just a heads-up. Thanks again. On Wed, Jul 6, 2016 at 7:51 PM, Steven Hartland <killing@multiplay.co.uk> wrote: > On 06/07/2016 21:39, Eric van Gyzen wrote: > >> On 07/06/16 03:35 PM, Steven Hartland wrote: >> >>> The ARC settings and kmem aren't initialised when tunables are loaded >>> so the tests fail. >>> >>> I've fixed this locally by blindly setting if ARC is not configured. >>> Request to commit the fix is with re@ >>> >>> In the mean time the patch is attached. >>> >>> Thanks for the report and sorry about the breakage. >>> >> No worries. Thanks for the quick fix. >> >> https://svnweb.freebsd.org/changeset/base/302382 > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAB%2BRvm5o_Xc3Ufyj1%2B3rN26cEbTwuQ_rpk1RDgi8HZ0c346JhA>