Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 02 Mar 2019 12:07:46 +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-D9Hl3cGM8j@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 #19 from Graham Perrin <grahamperrin@gmail.com> ---
A year or so ago, before I was aware of this bug, I had a sense that things
weren't right on a notebook with 15.9 GiB memory. Probably 12.0-CURRENT at =
the
time.=20

IIRC I chose to set vfs.zfs.arc_max to around 2 G. (I can't recall what mad=
e me
choose that figure =E2=80=A6 something in bug 187594, maybe. I vaguely reca=
ll 2 G being
around half of the default but that seems inconsistent with what I now read=
 at
<https://www.freebsd.org/doc/handbook/zfs-advanced.html>.)=20

Whilst I didn't take measurements, the end result was pleasing.=20

With a cleaner installation of 13.0-CURRENT (~2018-12), I have not (yet) fe=
lt
the need to change vfs.zfs.arc_max

----

Today:=20

grahamperrin@momh167-gjp4-8570p:~ % date ; uname -v ; uptime
Sat  2 Mar 2019 11:43:54 GMT
FreeBSD 13.0-CURRENT r344443 GENERIC-NODEBUG=20
11:43a.m.  up 41 mins, 6 users, load averages: 1.02, 0.70, 0.61
grahamperrin@momh167-gjp4-8570p:~ % sysctl -a | grep vfs.zfs.arc
vfs.zfs.arc_min_prescient_prefetch_ms: 6
vfs.zfs.arc_min_prefetch_ms: 1
vfs.zfs.arc_meta_strategy: 0
vfs.zfs.arc_meta_limit: 3883606016
vfs.zfs.arc_free_target: 86433
vfs.zfs.arc_kmem_cache_reap_retry_ms: 0
vfs.zfs.arc_grow_retry: 60
vfs.zfs.arc_shrink_shift: 7
vfs.zfs.arc_average_blocksize: 8192
vfs.zfs.arc_no_grow_shift: 5
vfs.zfs.arc_min: 1941803008
vfs.zfs.arc_max: 15534424064
grahamperrin@momh167-gjp4-8570p:~ % sysctl -a | grep vnode
kern.maxvnodes: 348816
kern.ipc.umtx_vnode_persistent: 0
kern.minvnodes: 87204
Syncing disks, vnodes remaining... 0 0 0 0 0 0 done
Syncing disks, vnodes remaining... 0 0 0 0 0 0 done
Syncing disks, vnodes remaining... 0 0 0 0 0 done
vm.vnode_pbufs: 512
vm.stats.vm.v_vnodepgsout: 3703
vm.stats.vm.v_vnodepgsin: 126117
vm.stats.vm.v_vnodeout: 1842
vm.stats.vm.v_vnodein: 12321
vfs.freevnodes: 9195
vfs.wantfreevnodes: 87204
vfs.vnodes_created: 19046
vfs.numvnodes: 16690
vfs.cache.cache_lock_vnodes_cel_3_failures: 0
vfs.ncpurgeminvnodes: 512
debug.vnode_domainset: <NULL>
debug.sizeof.vnode: 480
debug.fail_point.status_fill_kinfo_vnode__random_path: off
debug.fail_point.fill_kinfo_vnode__random_path: off
grahamperrin@momh167-gjp4-8570p:~ %=20

----

Now added to /etc/sysctl.conf :

vfs.zfs.arc_max=3D"2147483648"

If I'm to add a setting for kern.maxvnodes =E2=80=93for test purposes =E2=
=80=93 what would you
suggest?

TIA

--=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-D9Hl3cGM8j>