From owner-freebsd-fs@FreeBSD.ORG Wed Jan 25 11:59:14 2012 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 E69071065672 for ; Wed, 25 Jan 2012 11:59:14 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [76.96.30.56]) by mx1.freebsd.org (Postfix) with ESMTP id C7A928FC0A for ; Wed, 25 Jan 2012 11:59:14 +0000 (UTC) Received: from omta06.emeryville.ca.mail.comcast.net ([76.96.30.51]) by qmta06.emeryville.ca.mail.comcast.net with comcast id RnxR1i00216AWCUA6nzEnh; Wed, 25 Jan 2012 11:59:14 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta06.emeryville.ca.mail.comcast.net with comcast id RnzD1i00C1t3BNj8SnzD0D; Wed, 25 Jan 2012 11:59:13 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 4B0D4102C19; Wed, 25 Jan 2012 03:59:13 -0800 (PST) Date: Wed, 25 Jan 2012 03:59:13 -0800 From: Jeremy Chadwick To: Michel Le Cocq Message-ID: <20120125115913.GA30376@icarus.home.lan> References: <201110091940.p99JeJIc095036@freefall.freebsd.org> <20120125084040.GA2831@e4310> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120125084040.GA2831@e4310> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Garrett Cooper , freebsd-fs@FreeBSD.org Subject: Re: kern/146528: [zfs] Severe memory leak in ZFS on i386 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: Wed, 25 Jan 2012 11:59:15 -0000 On Wed, Jan 25, 2012 at 09:40:50AM +0100, Michel Le Cocq wrote: > Before upgrade, I must use some mana things in my /boot/loader.conf > > vm.kmem_size="330M" > vm.kmem_size_max="330M" > vfs.zfs.arc_max="40M" > vfs.zfs.vdev.cache.size="5M" > > With this config my server was not so stable. > > Some days it work perfectly, some others it freeze with kmem_malloc > kmem_map too small. > Without this mana it freeze really often. You should remove the vm.kmem_size and vm.kmem_size_max settings from loader.conf. (This is at least the case for amd64, and I'm pretty sure the same advice applies to i386. The lack-of need for adjusting either of these variables has existed for, I think, a year now.) The other options you have specific to ZFS can stay. Also, your ARC maximum is extremely low; can you please increase this to something more reasonable, say, 256MBytes or 384MBytes? This may explain the "freeze really often" clause, assuming you mean "the system suddenly pauses, takes a while, then recovers". If by "freeze really often" you mean "locks up hard", that's a different problem. If the freezing is intermittent (and recovers), are you using dedup or compression? If so, please cease. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |