Date: Tue, 28 Sep 2010 15:22:01 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: stable@freebsd.org, fs@freebsd.org Subject: Re: Still getting kmem exhausted panic Message-ID: <4CA1DDE9.8090107@icyb.net.ua> In-Reply-To: <20100928115047.GA62142__15392.0458550148$1285675457$gmane$org@icarus.home.lan> References: <4CA1D06C.9050305@digiware.nl> <20100928115047.GA62142__15392.0458550148$1285675457$gmane$org@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
on 28/09/2010 14:50 Jeremy Chadwick said the following: > I believe the trick -- Andriy, please correct me if I'm wrong -- is the Wouldn't hurt to CC me, so that I could do it :-) > tuning of vfs.zfs.arc_max, which is now a hard limit rather than a "high > watermark". Not sure what you mean here. What is hard limit, what is high watermark, what is the difference and when is "now"? :-) I believe that "the trick" is to set vm.kmem_size high enough, eitehr using this tunable or vm.kmem_size_scale. > However, I believe there have been occasional reports of exhaustion > panics despite both of these being set[1]. Those reports are being > investigated on an individual basis. I don't believe that the report that you quote actually demonstrates what you say it does. Two quotes from it: "During these panics no tuning or /boot/loader.conf values where present." "Only after hitting this behaviour yesterday i created boot/loader.conf" > > [1]: http://lists.freebsd.org/pipermail/freebsd-stable/2010-September/059109.html > -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CA1DDE9.8090107>