From owner-freebsd-fs@FreeBSD.ORG Wed Jan 25 11:19:58 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 34504106564A for ; Wed, 25 Jan 2012 11:19:57 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id B86A28FC12 for ; Wed, 25 Jan 2012 11:19:56 +0000 (UTC) Received: by bkbc12 with SMTP id c12so5727217bkb.13 for ; Wed, 25 Jan 2012 03:19:55 -0800 (PST) Received: by 10.205.141.76 with SMTP id jd12mr6852922bkc.42.1327488507181; Wed, 25 Jan 2012 02:48:27 -0800 (PST) Received: from dfleuriot-at-hi-media.com ([83.167.62.196]) by mx.google.com with ESMTPS id sp6sm19439bkb.2.2012.01.25.02.48.25 (version=SSLv3 cipher=OTHER); Wed, 25 Jan 2012 02:48:26 -0800 (PST) Message-ID: <4F1FDDF8.6020300@my.gd> Date: Wed, 25 Jan 2012 11:48:24 +0100 From: Damien Fleuriot User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <201110091940.p99JeJIc095036@freefall.freebsd.org> <20120125084040.GA2831@e4310> <4F1FD252.4090403@brockmann-consult.de> In-Reply-To: <4F1FD252.4090403@brockmann-consult.de> X-Gm-Message-State: ALoCoQkUlToANPxwpjp/LVfoEl/+VSENPYpGTTKmApHuJtVRbhDX5F7pLhYgdw8q4P/9oycbH5IO Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit 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:19:58 -0000 Hijacking thread quickly. How do you guys usually check your build/csup date on -stable and such ? I guess I'd go with the latest kernel build date, but there may be better ways. On 1/25/12 10:58 AM, Peter Maloney wrote: > When was your 8.2-STABLE built / csup'd? > > Peter > > > On 01/25/2012 09:40 AM, Michel Le Cocq wrote: >> Hi every body, I upgrade my Freebsd 8.2-STABLE i386 to 9.0 i386. >> Intel(R) Atom(TM) CPU D510 @ 1.66GHz >> real memory = 4294967296 (4096 MB) >> avail memory = 3127390208 (2982 MB) >> >> I'm on a ZFS Root file systeme on 2 USB drive and 6 sata drive for >> data. >> >> # zpool list >> NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT >> data 931G 254G 677G 27% 1.00x ONLINE - >> stock 74.5G 12.4G 62.1G 16% 1.00x ONLINE - >> tank 696G 574G 122G 82% 1.00x ONLINE - >> zroot 3.66G 2.49G 1.17G 67% 1.00x ONLINE - >> >> 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. >> >> The thing which make me upgrade is that after one of this crash after >> reboot it won't mount my data pool which was at 99% of his CAP. The >> only way I find to boot is to disconnect the pools drive and export >> it. >> >> Now I'm on exactly the same host after upgrade to 9.0 and it seems to >> work really really better (3 days up with out any trouble). >> >> -- >> M >> >> Garrett Cooper a écrit: >>> The following reply was made to PR kern/146528; it has been noted by GNATS. >>> >>> From: Garrett Cooper >>> To: bug-followup@FreeBSD.org, EdwinGuy@GMail.com >>> Cc: >>> Subject: Re: kern/146528: [zfs] Severe memory leak in ZFS on i386 >>> Date: Sun, 9 Oct 2011 12:34:00 -0700 >>> >>> Could you please try upgrading to 8.2-STABLE or 9.0 and see if the >>> issue persists with ZFS v28? >>> -Garrett >>> _______________________________________________ >>> freebsd-fs@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >>> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > >