From owner-freebsd-fs@FreeBSD.ORG Fri May 28 13:45:53 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 545951065678 for ; Fri, 28 May 2010 13:45:53 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by mx1.freebsd.org (Postfix) with ESMTP id 02A588FC13 for ; Fri, 28 May 2010 13:45:52 +0000 (UTC) Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by qmta02.westchester.pa.mail.comcast.net with comcast id NyJz1e0010bG4ec521lt4K; Fri, 28 May 2010 13:45:53 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta03.westchester.pa.mail.comcast.net with comcast id P1lq1e00N3S48mS3P1lrSc; Fri, 28 May 2010 13:45:52 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 7D1229B418; Fri, 28 May 2010 06:45:49 -0700 (PDT) Date: Fri, 28 May 2010 06:45:49 -0700 From: Jeremy Chadwick To: Andriy Gapon Message-ID: <20100528134549.GA75411@icarus.home.lan> References: <060401cafe37$a411b240$ec3516c0$@net> <4BFF894F.4010008@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BFF894F.4010008@icyb.net.ua> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: amd64@freebsd.org, freebsd-fs@freebsd.org Subject: Re: FreeBSD 8.1-Prerelease Panic amd64 w/ZFS.. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 May 2010 13:45:53 -0000 On Fri, May 28, 2010 at 12:13:51PM +0300, Andriy Gapon wrote: > on 28/05/2010 10:30 Howard Leadmon said the following: > > I know there used to be some issues with this a while back, but thought > > with the 8.x FBSD servers most of this tuned itself, or then again maybe > > this is something different. > > > > > > > > For the first time I ever recall, I found my FreeBSD 8 server was crashed > > this past morning, with the following error: > > > > > > > > panic:kmem_malloc(131072):kmem_map to small: 1296826368 total allocated > > > > cupid=4 > > O wow, this is an amd64 system (with 4G RAM) and you've got "kmem_map too > small". That's very very strange. It is? On amd64, vm.kmem_size (not vm.kmem_size_max) is what has to be increased. I can point folks to the "official" statement from pjd@ and some others if need be. For a very long time I questioned this because for an even longer amount of time we were being told to increase vm.kmem_size_max. vm.kmem_size_max, by default, is already huge on amd64 (~320GB or something like that). Proof: vm.kmem_size_max: 329853485875 To the OP: you will need to increase vm.kmem_size in /boot/loader.conf and reboot the system. "What value do I pick?" With 4GB, I would recommend you use these two variables: vm.kmem_size="2048M" vfs.zfs.arc_max="1536M" This will increase the available kmem, and also limit the ARC size explicitly to nothing larger than 1.5GB. This should stabilise your system. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |