From owner-freebsd-current@FreeBSD.ORG Tue Jul 29 08:34:04 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0EB9F106567E; Tue, 29 Jul 2008 08:34:04 +0000 (UTC) (envelope-from remy.nonnenmacher@activnetworks.com) Received: from maiev.nerim.net (maiev.ipv6.nerim.net [IPv6:2001:7a8:1:1::89]) by mx1.freebsd.org (Postfix) with ESMTP id A4DA38FC0C; Tue, 29 Jul 2008 08:34:03 +0000 (UTC) (envelope-from remy.nonnenmacher@activnetworks.com) Received: from rn.activnetworks.com (anwadmin.net8.nerim.net [213.41.185.85]) by maiev.nerim.net (Postfix) with ESMTP id A8CCBB9DC6; Tue, 29 Jul 2008 10:34:01 +0200 (CEST) Message-ID: <488ED5F9.3090004@activnetworks.com> Date: Tue, 29 Jul 2008 10:34:01 +0200 From: Remy Nonnenmacher User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.13) Gecko/20080327 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20080727125413.GG1345@garage.freebsd.pl> In-Reply-To: <20080727125413.GG1345@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: ZFS patches. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jul 2008 08:34:04 -0000 Pawel Jakub Dawidek wrote: > Hi. > > http://people.freebsd.org/~pjd/patches/zfs_20080727.patch.bz2 >... > Please test, test, test. If I get enough positive feedback, I may be > able to squeeze it into 7.1-RELEASE, but this might be hard. > > If you have any questions, please use mailing lists > (freebsd-fs@FreeBSD.org would be the best). > > Thank you in advance! > Hello, I have updated a test machine with the patch. Before the patch, the machine was fairly stable using vm.kmem_size=1024M and vfs.zfs.arc_max=200M. After the patch, I ran a few test with the following loader.conf: vm.kmem_size="512M" vm.kmem_size_max="512M" zfs_load="YES" vfs.zfs.arc_max="100M" kern.maxvnodes="400000" I am now getting back "kmem_map too small" panics within a few minutes of cvs update of ports. If I have a look at kstat.zfs.misc.arcstats.size in the mean time, I see the following: kstat.zfs.misc.arcstats.size: 275762656 kstat.zfs.misc.arcstats.size: 279666312 kstat.zfs.misc.arcstats.size: 284994776 kstat.zfs.misc.arcstats.size: 298142184 kstat.zfs.misc.arcstats.size: 304219168 kstat.zfs.misc.arcstats.size: 312289376 kstat.zfs.misc.arcstats.size: 318243832 kstat.zfs.misc.arcstats.size: 331942168 kstat.zfs.misc.arcstats.size: 335262560 kstat.zfs.misc.arcstats.size: 344793136 kstat.zfs.misc.arcstats.size: 359504168 kstat.zfs.misc.arcstats.size: 334877376 kstat.zfs.misc.arcstats.size: 334877376 kstat.zfs.misc.arcstats.size: 334877376 kstat.zfs.misc.arcstats.size: 334877376 kstat.zfs.misc.arcstats.size: 334877376 ((panic here)) (2 seconds between reads) It seems that arc_max is ignored or arc_reclaim is not working as expected. Tanks for your work, Pawel.