Date: Sun, 03 Feb 2019 05:38:59 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 229670] Too many vnodes causes ZFS ARC to exceed limit vfs.zfs.arc_max (high ARC "Other" usage) Message-ID: <bug-229670-3630-aTjwVaD9O6@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-229670-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-229670-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=3D229670 --- Comment #17 from Leif Pedersen <leif@ofWilsonCreek.com> --- In 11, I could lower vfs.zfs.arc_max without rebooting. If I lowered it bel= ow the current allocation, it'd whack out a bunch of cached data to get within= the new setting (maxvnodes problem notwithstanding). In 12, it seems I can't lower it below the current allocation. In practice, this means one will rarely be able to lower it without rebooting (since one wouldn't be trying to lower it on a running system unless it was already so large it was causing a problem). It was nice to be able to change it to make more room for hungry things like InnoDB without rebooting. Is that intentional? I guess there may be a good reason why, or maybe it ba= cks off automatically better than in 11? --=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-229670-3630-aTjwVaD9O6>