From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 5 13:24:56 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A32E1106564A for ; Thu, 5 Jun 2008 13:24:56 +0000 (UTC) (envelope-from hugo@barafranca.com) Received: from mail.barafranca.com (mail.barafranca.com [67.213.67.47]) by mx1.freebsd.org (Postfix) with ESMTP id 5B6288FC1E for ; Thu, 5 Jun 2008 13:24:56 +0000 (UTC) (envelope-from hugo@barafranca.com) Received: from localhost (unknown [172.16.100.24]) by mail.barafranca.com (Postfix) with ESMTP id BBD8E15CB; Thu, 5 Jun 2008 13:10:27 +0000 (UTC) X-Virus-Scanned: amavisd-new at barafranca.com Received: from mail.barafranca.com ([172.16.100.24]) by localhost (mail.barafranca.com [172.16.100.24]) (amavisd-new, port 10024) with ESMTP id 3r-VGDJp-mBB; Thu, 5 Jun 2008 13:09:50 +0000 (UTC) Received: from nexus.bsdlan.org (a213-22-25-165.cpe.netcabo.pt [213.22.25.165]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.barafranca.com (Postfix) with ESMTPSA id 1F05015BD; Thu, 5 Jun 2008 13:09:49 +0000 (UTC) Message-ID: <4847E5AA.5010109@barafranca.com> Date: Thu, 05 Jun 2008 14:10:02 +0100 From: Hugo Silva User-Agent: Thunderbird 2.0.0.6 (X11/20070816) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <6a7033710805302252v43a7b240x66ca3f5e3dd5fda4@mail.gmail.com> <20080603135308.GC3434@garage.freebsd.pl> <6a7033710806032317g4dbe8845h26a1196016b9c440@mail.gmail.com> <86zlq140x0.fsf@ds4.des.no> <6a7033710806041053g4a5c2fdftd7202b708bff363c@mail.gmail.com> <20080605062728.GA4278@garage.freebsd.pl> In-Reply-To: <20080605062728.GA4278@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Is there any way to increase the KVM? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jun 2008 13:24:56 -0000 Pawel Jakub Dawidek wrote: > On Thu, Jun 05, 2008 at 01:53:37AM +0800, Tz-Huan Huang wrote: > >> On Thu, Jun 5, 2008 at 12:31 AM, Dag-Erling Sm??rgrav wrote: >> >>> "Tz-Huan Huang" writes: >>> >>>> The vfs.zfs.arc_max was set to 512M originally, the machine survived for >>>> 4 days and panicked this morning. Now the vfs.zfs.arc_max is set to 64M >>>> by Oliver's suggestion, let's see how long it will survive. :-) >>>> >>> des@ds4 ~% uname -a >>> FreeBSD ds4.des.no 8.0-CURRENT FreeBSD 8.0-CURRENT #27: Sat Feb 23 01:24:32 CET 2008 des@ds4.des.no:/usr/obj/usr/src/sys/ds4 amd64 >>> des@ds4 ~% sysctl -h vm.kmem_size_min vm.kmem_size_max vm.kmem_size vfs.zfs.arc_min vfs.zfs.arc_max >>> vm.kmem_size_min: 1,073,741,824 >>> vm.kmem_size_max: 1,073,741,824 >>> vm.kmem_size: 1,073,741,824 >>> vfs.zfs.arc_min: 67,108,864 >>> vfs.zfs.arc_max: 536,870,912 >>> des@ds4 ~% zpool list >>> NAME SIZE USED AVAIL CAP HEALTH ALTROOT >>> raid 1.45T 435G 1.03T 29% ONLINE - >>> des@ds4 ~% zfs list | wc -l >>> 210 >>> >>> Haven't had a single panic in over six months. >>> >> Thanks for your information, the major difference is that we >> runs on 7-stable and the size of our zfs pool is much bigger. >> > > I'm don't think the panics are related to pool size. More to the load > and characteristics of your workload. > > >> root@cml2$ uname -a >> FreeBSD cml2.csie.ntu.edu.tw 7.0-STABLE FreeBSD 7.0-STABLE #40: Sat >> May 31 10:29:16 CST 2008 >> root@cml2.csie.ntu.edu.tw:/usr/local/obj/usr/local/src/sys/CML2 amd64 >> root@cml2$ sysctl -h vm.kmem_size_min vm.kmem_size_max vm.kmem_size >> vfs.zfs.arc_min vfs.zfs.arc_max >> vm.kmem_size_min: 0 >> vm.kmem_size_max: 1,610,612,736 >> vm.kmem_size: 1,610,612,736 >> vfs.zfs.arc_min: 16,777,216 >> vfs.zfs.arc_max: 67,108,864 >> root@cml2$ zpool list >> NAME SIZE USED AVAIL CAP HEALTH ALTROOT >> sun 11.3T 9.03T 2.30T 79% ONLINE - >> root@cml2$ zfs list | wc -l >> 295 >> > > If we're comparing who has bigger... :) > > beast:root:~# zpool list > NAME SIZE USED AVAIL CAP HEALTH ALTROOT > tank 732G 604G 128G 82% ONLINE - > > but: > > beast:root:~# zfs list | wc -l > 1932 > > No panics. > > PS. I'm quite sure the ZFS version I've in perforce will fix most if not > all 'kmem_map too small' panics. It's not yet committed, but I do want > to MFC it into RELENG_7. > > Any guesstimate as to when the MFC will happen ?