From owner-freebsd-current@FreeBSD.ORG Thu Sep 13 22:26:31 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 97BCC16A418; Thu, 13 Sep 2007 22:26:31 +0000 (UTC) (envelope-from lists@avioc.org) Received: from didy.avioc.org (didy.avioc.org [71.32.26.53]) by mx1.freebsd.org (Postfix) with ESMTP id 4CECF13C46C; Thu, 13 Sep 2007 22:26:31 +0000 (UTC) (envelope-from lists@avioc.org) Received: from localhost (mail.internal.avioc.org [192.168.2.252]) by didy.avioc.org (Postfix) with ESMTP id 95FDBEB644E; Thu, 13 Sep 2007 17:09:06 -0500 (CDT) X-Virus-Scanned: amavisd-new at mail.internal.avioc.org Received: from didy.avioc.org ([192.168.2.252]) by localhost (mail.internal.avioc.org [192.168.2.252]) (amavisd-new, port 10024) with LMTP id L1p3oxcfnGkq; Thu, 13 Sep 2007 17:09:03 -0500 (CDT) Received: from [192.168.2.8] (section-8.internal.avioc.org [192.168.2.8]) by didy.avioc.org (Postfix) with ESMTP id 5CE16EB644D; Thu, 13 Sep 2007 17:09:03 -0500 (CDT) From: Brandon Weisz To: Joao Barros In-Reply-To: <70e8236f0709131425h2f651c32j5e23d7901ce6e1f7@mail.gmail.com> References: <20070906184853.GB90021@roadrunner.spoerlein.net> <20070910195833.GE1103@garage.freebsd.pl> <70e8236f0709131425h2f651c32j5e23d7901ce6e1f7@mail.gmail.com> Content-Type: text/plain Date: Thu, 13 Sep 2007 17:09:03 -0500 Message-Id: <1189721343.17751.20.camel@section-8.ipv6.avioc.org> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 Content-Transfer-Encoding: 7bit Cc: Pawel Jakub Dawidek , current@freebsd.org Subject: Re: ZFS not caching right? 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: Thu, 13 Sep 2007 22:26:31 -0000 On Thu, 2007-09-13 at 22:25 +0100, Joao Barros wrote: > On 9/10/07, Pawel Jakub Dawidek wrote: > > On Thu, Sep 06, 2007 at 08:48:53PM +0200, Ulrich Spoerlein wrote: > > > Hi, it's me again with another stupid question, > > > > > > ever since I switched my /usr and /home to ZFS, the system has become > > > _very_ unresponsive under load. This is not because of CPU load, but I/O > > > load. > > > > Can you try recent HEAD? I committed a change that allows ZFS cache > > (ARC) to use more memory. This should be safe after dfr@'s vnode leak > > fix and should also help performance. > > > > -- > > Pawel Jakub Dawidek http://www.wheel.pl > > pjd@FreeBSD.org http://www.FreeBSD.org > > FreeBSD committer Am I Evil? Yes, I Am! > > > > > > This happened 1 day after compiling new sources: > panic: kmem_malloc(90112): kmem_map too small: 329805824 total allocated > when writing through NFS. > On FreeBSD xeon.bsdtech.org 7.0-CURRENT FreeBSD 7.0-CURRENT #8: Tue > Sep 11 00:08:39 WEST 2007 > root@xeon.bsdtech.org:/usr/obj/usr/src/sys/GENERIC i386 > Machine has 1GB of ram and: > vfs.zfs.arc_min: 16777216 > vfs.zfs.arc_max: 251658240 > vfs.zfs.mdcomp_disable: 0 > vfs.zfs.prefetch_disable: 1 > vfs.zfs.zio.taskq_threads: 0 > vfs.zfs.recover: 0 > vfs.zfs.vdev.cache.size: 10485760 > vfs.zfs.vdev.cache.max: 16384 > vfs.zfs.cache_flush_disable: 0 > vfs.zfs.zil_disable: 0 > vfs.zfs.debug: 0 > > I hadn't had any panics with sources from August 16 but before your > recent changes vfs.zfs.arc_max was 167772160 > kern.maxvnodes is not set to 50000 as recomended ( on purpose ) and is > currently at 52242 set by the system. Is 50000 still recomended after > your changes? > Just a "me too" - I am also seeing "kmem_map too small" panics on a amd64 NFS server with 1 GB ram after the recent zfs changes. setting vm.kmem_size_max="402653184" seems to have stopped the panics, however this was not needed previously. Brandon