[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-fs
Subject:    [Bug 265424] vfs.zfs.arc_min ignored in /boot/loader.conf but works in /etc/sysctl.conf
From:       bugzilla-noreply () freebsd ! org
Date:       2022-07-26 15:43:41
Message-ID: bug-265424-3630-sZsqZlW5UJ () https ! bugs ! freebsd ! org/bugzilla/
[Download RAW message or body]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265424

--- 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 assume
it also may be the recommended method to access that property) is with the
underscore (arc_min, arc_max)?

- Jonathan

-- 
You are receiving this mail because:
You are the assignee for the bug.
[prev in list] [next in list] [prev in thread] [next in thread]