From owner-freebsd-fs@FreeBSD.ORG  Tue Sep 28 12:37:28 2010
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id D35BC106564A
	for <fs@freebsd.org>; Tue, 28 Sep 2010 12:37:28 +0000 (UTC)
	(envelope-from avg@icyb.net.ua)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
	by mx1.freebsd.org (Postfix) with ESMTP id 1E7FF8FC0C
	for <fs@freebsd.org>; Tue, 28 Sep 2010 12:37:27 +0000 (UTC)
Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua
	[212.40.38.101])
	by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA03464;
	Tue, 28 Sep 2010 15:22:02 +0300 (EEST)
	(envelope-from avg@icyb.net.ua)
Message-ID: <4CA1DDE9.8090107@icyb.net.ua>
Date: Tue, 28 Sep 2010 15:22:01 +0300
From: Andriy Gapon <avg@icyb.net.ua>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US;
	rv:1.9.2.9) Gecko/20100920 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: Jeremy Chadwick <freebsd@jdc.parodius.com>
References: <4CA1D06C.9050305@digiware.nl>
	<20100928115047.GA62142__15392.0458550148$1285675457$gmane$org@icarus.home.lan>
In-Reply-To: <20100928115047.GA62142__15392.0458550148$1285675457$gmane$org@icarus.home.lan>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: stable@freebsd.org, fs@freebsd.org
Subject: Re: Still getting kmem exhausted panic
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Sep 2010 12:37:28 -0000

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