From owner-freebsd-stable@FreeBSD.ORG Mon May 10 16:03:15 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 75B3A1065674 for ; Mon, 10 May 2010 16:03:15 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [76.96.59.212]) by mx1.freebsd.org (Postfix) with ESMTP id 22DDF8FC17 for ; Mon, 10 May 2010 16:03:14 +0000 (UTC) Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by qmta14.westchester.pa.mail.comcast.net with comcast id FnJo1e0031vXlb85Es3FvS; Mon, 10 May 2010 16:03:15 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta17.westchester.pa.mail.comcast.net with comcast id Fs3E1e0013S48mS3ds3E2T; Mon, 10 May 2010 16:03:15 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 8EE919B425; Mon, 10 May 2010 09:03:12 -0700 (PDT) Date: Mon, 10 May 2010 09:03:12 -0700 From: Jeremy Chadwick To: Mike Andrews Message-ID: <20100510160312.GA62178@icarus.home.lan> References: <4BDEA86E.3050109@zirakzigil.org> <20100503110100.GA93137@icarus.home.lan> <4BDEC106.3040807@zirakzigil.org> <4BE110E3.8040902@zirakzigil.org> <4BE82C5D.1080806@bit0.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BE82C5D.1080806@bit0.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-stable@freebsd.org Subject: Re: Freebsd 8.0 kmem map too small X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 May 2010 16:03:15 -0000 On Mon, May 10, 2010 at 11:55:09AM -0400, Mike Andrews wrote: > Sorry to semi-hijack this, but... I'm also running into frequent > "kmem_map too small" panics on 8-STABLE, such as: > > panic: kmem_malloc(131072): kmem_map too small: 2023780352 total allocated > panic: kmem_malloc(131072): kmem_map too small: 2011525120 total allocated > panic: kmem_malloc(114688): kmem_map too small: 1849356288 total allocated > panic: kmem_malloc(114688): kmem_map too small: 1849356288 total allocated > panic: kmem_malloc(114688): kmem_map too small: 1849356288 total allocated > panic: kmem_malloc(131072): kmem_map too small: 2020409344 total allocated > panic: kmem_malloc(536576): kmem_map too small: 2022957056 total allocated > > (those are over the course of 3-4 days) > > On this specific system, it has 32 GB physical memory and has > vfs.zfs.arc_max="2G" and vm.kmem_size="64G" in /boot/loader.conf. > The latter was added per earlier suggestions on this list, but > appears to be ignored as "sysctl vm.kmem_size" returns about 2 GB > (2172452864) anyway. > > ... In your case, vm.kmem_size being stuck at 2GB (despite you setting it larger) is the problem. A workaround would be for you to set vfs.zfs.arc_max to something smaller, such as 1G or 512M. Can you please provide output from the following 5 commands: uname -a sysctl vm.kmem_size_min vm.kmem_size_max vm.kmem_size vm.kmem_size_scale sysctl hw.physmem hw.usermem hw.realmem sysctl hw.machine_arch sysctl hw.pagesize hw.pagesizes hw.availpages Thanks. -- | 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 |