From owner-freebsd-stable@FreeBSD.ORG Thu Sep 25 13:29:44 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 62BA71065687 for ; Thu, 25 Sep 2008 13:29:44 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0803A8FC1F for ; Thu, 25 Sep 2008 13:29:43 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m8PDTWLV095309; Thu, 25 Sep 2008 09:29:38 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-stable@freebsd.org Date: Thu, 25 Sep 2008 08:25:19 -0400 User-Agent: KMail/1.9.7 References: <48DB6772.1060400@kkip.pl> In-Reply-To: <48DB6772.1060400@kkip.pl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809250825.19757.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Thu, 25 Sep 2008 09:29:38 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/8329/Thu Sep 25 04:47:46 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Bartosz Stec Subject: Re: vm.kmem_size settings doesn't affect loader? 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: Thu, 25 Sep 2008 13:29:44 -0000 On Thursday 25 September 2008 06:26:58 am Bartosz Stec wrote: > > Today I've experienced zfs-related kernel panic. Log says: > > savecore: reboot after panic: kmem_malloc(131072): kmem_map too > small: 327684096 total allocated > > Reported amount of memory (327684096) is wrong, because i made suggested > tuning in my loader.conf: > > vm.kmem_size="512M" > vm.kmem_size_max="512M" > > Just to be sure: > > # sysctl vm | grep kmem > vm.kmem_size: 536870912 > vm.kmem_size_min: 0 > vm.kmem_size_max: 536870912 > vm.kmem_size_scale: 3 > > Am I missing something? If kvm is fragmented you could have a malloc fail even if there are enough total free bytes for the allocatoin. -- John Baldwin