From owner-freebsd-current@FreeBSD.ORG Wed Jun 20 20:17:29 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2CBF116A469 for ; Wed, 20 Jun 2007 20:17:29 +0000 (UTC) (envelope-from mack@macktronics.com) Received: from coco.macktronics.com (coco.macktronics.com [209.181.253.65]) by mx1.freebsd.org (Postfix) with ESMTP id EFD2713C448 for ; Wed, 20 Jun 2007 20:17:28 +0000 (UTC) (envelope-from mack@macktronics.com) Received-SPF: none (coco.macktronics.com: 209.181.253.65 is neither permitted nor denied by domain of macktronics.com) client-ip=209.181.253.65; envelope-from=mack@macktronics.com; helo=coco.macktronics.com; Received: from coco.macktronics.com (coco.macktronics.com [209.181.253.65]) by coco.macktronics.com (Postfix) with ESMTP id 6DA694AC11; Wed, 20 Jun 2007 14:56:13 -0500 (CDT) Date: Wed, 20 Jun 2007 14:56:13 -0500 (CDT) From: Dan Mack To: John Nielsen In-Reply-To: <200706201528.31349.lists@jnielsen.net> Message-ID: <20070620145130.K71819@coco.macktronics.com> References: <1182354823.6504.23.camel@shumai.marcuscom.com> <20070620160306.GA74674@rot26.obsecurity.org> <20070620111405.K71264@coco.macktronics.com> <200706201528.31349.lists@jnielsen.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: ZFS and deadlock with {nullfs,NFS} 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: Wed, 20 Jun 2007 20:17:29 -0000 On Wed, 20 Jun 2007, John Nielsen wrote: > On Wednesday 20 June 2007 12:30:23 pm Dan Mack wrote: >> On Wed, 20 Jun 2007, Kris Kennaway wrote: >> >> >> >>> 404 at the moment, but look for processes involving zil* in the >>> backtrace. I had to disable zil (vfs.zfs.zil_disable=1 tunable) to >>> prevent low-memory deadlocks on my machines. Since then it's been >>> fine. >>> >>> You may also wish to use my patches (see the archives) to improve >>> performance and low-memory behaviour. >>> >>> Kris >> >> Does someone have these recommended sysctls embodied in an example >> /boot/loader.conf yet? Here is mine, does it look reasonable to keep ZFS >> from running into the kmem_ memory panics? I have no idea if I found all >> of your recommendations so it would be nice if they were summarized in one >> place. >> >> | # /boot/loader.conf i386 / 1GB memory / SMP >> | kern.maxvnodes="50000" > > Note that kern.maxvnodes has to be set in /etc/sysctl.conf to have any effect. > > JN FWIW ... I'm still experiencing panics; this time with when running cvsup to update /usr/ports: borg# grep -i Panic /var/crash/info* /var/crash/info.0: Panic String: kmem_malloc(16384): kmem_map too small: 268419072 total allocated /var/crash/info.1: Panic String: kmem_malloc(131072): kmem_map too small: 266354688 total allocated /var/crash/info.2: Panic String: kmem_malloc(4096): kmem_map too small: 268435456 total allocated /var/crash/info.3: Panic String: kmem_malloc(28672): kmem_map too small: 268435456 total allocated Anyone ideas on other tunables that might keep the system running? I'm not too concerned about performance. Otherwise I'll have to go spend some money on an AMD64 mainboard, memory, and cpu :-( Dan