From owner-freebsd-current@FreeBSD.ORG  Tue Sep 25 04:55:55 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id D886E16A41B;
	Tue, 25 Sep 2007 04:55:55 +0000 (UTC)
	(envelope-from darrenr@freebsd.org)
Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com
	[66.111.4.25])
	by mx1.freebsd.org (Postfix) with ESMTP id 996CF13C49D;
	Tue, 25 Sep 2007 04:55:55 +0000 (UTC)
	(envelope-from darrenr@freebsd.org)
Received: from compute1.internal (compute1.internal [10.202.2.41])
	by out1.messagingengine.com (Postfix) with ESMTP id BD04E2FD1D;
	Tue, 25 Sep 2007 00:55:54 -0400 (EDT)
Received: from heartbeat2.messagingengine.com ([10.202.2.161])
	by compute1.internal (MEProxy); Tue, 25 Sep 2007 00:55:54 -0400
X-Sasl-enc: 5CuKcbdY4UWTInNW/CXK+W+/m3rHLW/PiOayNGjIttoy 1190696154
Received: from [192.168.1.235] (64-142-85-108.dsl.dynamic.sonic.net
	[64.142.85.108])
	by mail.messagingengine.com (Postfix) with ESMTP id 4ED7C22DC9;
	Tue, 25 Sep 2007 00:55:53 -0400 (EDT)
Message-ID: <46F8951C.50904@freebsd.org>
Date: Mon, 24 Sep 2007 21:57:00 -0700
From: Darren Reed <darrenr@freebsd.org>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: Kris Kennaway <kris@FreeBSD.org>
References: <20070921102946.T11189@borg>
	<46F415BF.9010500@FreeBSD.org>	<20070921140550.D96923@thebighonker.lerctr.org>	<46F41CFF.6080108@FreeBSD.org>
	<46F58799.1030702@freebsd.org>	<46F58B21.8030307@FreeBSD.org>	<20070924091558.GB32006@team.vega.ru>	<46F78C59.1020801@FreeBSD.org>	<20070924080347.O84223@thebighonker.lerctr.org>
	<20070924144210.GA82735@team.vega.ru>
	<46F7D7A4.5090007@samsco.org> <46F80A39.3050707@FreeBSD.org>
In-Reply-To: <46F80A39.3050707@FreeBSD.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org, Larry Rosenman <ler@lerctr.org>
Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Sep 2007 04:55:55 -0000

Kris Kennaway wrote:
> ...
> Well yes, that is one hypothesis, but the evidence points elsewhere as 
> well.  Prior the change you reference, some of my zfs machines would 
> run for weeks before hitting a load pattern that exhausted their 
> kmem_map and triggered the panic.  Also unless I have missed it I am 
> not seeing the sudden flood of panic reports that may indicate sudden 
> breakage.  It is quite possible that this particular report has 
> nothing to do with the recent change.

Indeed.

But here's something else to ponder...

I've been using ZFS since it was internal beta at Sun, at first on i386 
and later on amd64.
I've never run into this kind of panic on Solaris.  System can get very 
slow, yes, with
ZFS hogging lots of memory, but it never panic'd because of it.

We need to come up with a strategy here to solve this problem, be it 
fixing the kmem
virtual memory or fixing zfs.

Darren