Date: Tue, 26 Jul 2022 15:43:41 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 265424] vfs.zfs.arc_min ignored in /boot/loader.conf but works in /etc/sysctl.conf Message-ID: <bug-265424-3630-sZsqZlW5UJ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-265424-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-265424-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D265424 --- Comment #2 from Jonathan Vasquez <jon@xyinn.org> --- Hey Graham, Thanks for that. I haven't tested it but even if that did end up working for /boot/loader.conf, it's still really unintuitive given that "arc_min" and "arc_max" are valid options as well. Of course one is under 'vfs.zfs' (more= top level) and one is under 'vfs.zfs.arc' as you mentioned. root@leslie:~ # sysctl vfs.zfs.arc.min vfs.zfs.arc.min: 4294967296 root@leslie:~ # sysctl vfs.zfs.arc.max vfs.zfs.arc.max: 8589934592 root@leslie:~ # sysctl vfs.zfs.arc_min vfs.zfs.arc_min: 4294967296 root@leslie:~ # sysctl vfs.zfs.arc_max vfs.zfs.arc_max: 8589934592 Any reason for the discrepancy? Is it a backwards compatibility reason? From the documentation, it seems the options mentioned (thus a reader would assu= me it also may be the recommended method to access that property) is with the underscore (arc_min, arc_max)? - Jonathan --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-265424-3630-sZsqZlW5UJ>