After running ZoF overnight, the various periodic scripts have kicked off, one of which runs "find" across the entire FS. This morning, while the system is still usable, the local pool is very slow, and I see the find process spending a lot of time in arc_recl state. Last time this occurred, bumping up arc_max immediately sped up the system and find command again.
arc metadata max isn't scaled back appropriately with low arc_max, so we revert to pruning only metadata if arc_max is less than 8G in 3ee97ec648ee61de4fe23f2bec842a90cd65ec69
After running ZoF overnight, the various periodic scripts have kicked off, one of which runs "find" across the entire FS. This morning, while the system is still usable, the local pool is very slow, and I see the find process spending a lot of time in arc_recl state. Last time this occurred, bumping up arc_max immediately sped up the system and find command again.
Here's as much relevant detail as I could find:
kstat.txt
Mav pointed out that the "2722M Other" is concerning. I have max_arc capped at 3000M in loader.conf.