From owner-freebsd-stable@FreeBSD.ORG Tue Oct 25 11:57:18 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D67116A41F for ; Tue, 25 Oct 2005 11:57:18 +0000 (GMT) (envelope-from for.bounces@dun.ukr.net) Received: from dun.ukr.net (dun.ukr.net [212.42.67.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54BDA43D6D for ; Tue, 25 Oct 2005 11:57:13 +0000 (GMT) (envelope-from for.bounces@dun.ukr.net) Received: from sharun by dun.ukr.net with local ID 1EUNQW-000KQK-GZ ; Tue, 25 Oct 2005 14:57:12 +0300 Date: Tue, 25 Oct 2005 14:57:12 +0300 From: Vladimir Sharun To: freebsd-stable@freebsd.org Message-ID: <20051025115712.GD55681@dun.ukr.net> Mail-Followup-To: Vladimir Sharun , freebsd-stable@freebsd.org, exim-users@exim.org References: <20051023074342.GA97095@dun.ukr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051023074342.GA97095@dun.ukr.net> User-Agent: Mutt/1.5.9i Cc: exim-users@exim.org Subject: Re: kmem_malloc(4096): kmem_map too small: 536870912 total allocated 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: Tue, 25 Oct 2005 11:57:18 -0000 I found the sources of the leak: if exim accessess ANY configuration/text files over NFS, there will be leak. And, how often exim will be called, then quicker your system dies. My main problem now is to build near-realtime mirroring solution nfs-to-local for around 20 files (up to 1Mb everything). Any /ports solution ? The next question to Philip Hazel: any comments why this happens ? Vladimir Sharun wrote: VS> We have 2xOpteron/2Gb RAM server with extensive disk load. Every week or two VS> it suddenly hangs with "kmem_malloc(4096): kmem_map too small 335bla-bla allocated". VS> I look onto handbook and put vm.kmem_size_max="536870912" onto /boot/loader.conf. VS> Today was the same with the new parameters. Is there any other solutions ? VS> # sysctl -a | grep kmem VS> vm.kmem_size: 536870912 VS> vm.kmem_size_max: 536870912 VS> vm.kmem_size_scale: 3 VS> The only vm.kmem_size_max on loader.conf, no vm.kmem_size. VS> We're running FreeBSD 6.0-BETA5 #0: Wed Sep 28 16:54:33 EEST 2005 VS> in i386 mode. The same was with 5.3/5.4 and NetBSD 2.0 on this machine.