Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 22 Sep 2018 12:23:06 +0930
From:      Shane Ambler <FreeBSD@ShaneWare.Biz>
To:        Mike Tancsa <mike@sentex.net>, Josh Gitlin <jgitlin@goboomtown.com>, freebsd-fs@freebsd.org
Subject:   Re: Troubleshooting kernel panic with zfs
Message-ID:  <41d177bf-117b-10c3-06a0-7d74d298fede@ShaneWare.Biz>
In-Reply-To: <c4d7e51f-09c9-c50c-075d-8eff65e64abe@sentex.net>
References:  <D54225AD-CC96-45E7-A203-D2C52E984963@goboomtown.com> <c4d7e51f-09c9-c50c-075d-8eff65e64abe@sentex.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 21/9/18 10:34 pm, Mike Tancsa wrote:
> 
> Given all the issues with memory pressure perhaps ARC is eating too
> much, I would try artificially limiting it so it does not eat up too
> much RAM.  We had a similar purposed server but with 32G RAM and I found
> one day the system was randomly shooting processes to reclaim RAM
> 
> eg
> pid xxx (yyy), uid zzzz, was killed: out of swap space
> 

I have seen these errors, for me they came when >90% ram is wired.

This is something I reported in bug 229764. While ARC is wired, there is
also a max_wired that limits other wired allocations, these two are
independent and can total more than physical ram.

max_wired defaults to 30% ram, so arc_max should be kept less than 70%

I also had positive results applying review D7538

-- 
FreeBSD - the place to B...Storing Data

Shane Ambler




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41d177bf-117b-10c3-06a0-7d74d298fede>