From owner-freebsd-current@FreeBSD.ORG Sat Jun 20 16:13:30 2009 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 E73E51065672 for ; Sat, 20 Jun 2009 16:13:30 +0000 (UTC) (envelope-from snb@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BB6F88FC18; Sat, 20 Jun 2009 16:13:30 +0000 (UTC) (envelope-from snb@freebsd.org) Received: from ebi.local (snb@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n5KGDT9w074536; Sat, 20 Jun 2009 16:13:29 GMT (envelope-from snb@freebsd.org) Date: Sat, 20 Jun 2009 18:13:28 +0200 From: Nick Barkas To: Kamigishi Rei Message-ID: <20090620161252.GA2885@ebi.local> References: <4A3B4260.6070200@haruhiism.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A3B4260.6070200@haruhiism.net> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: freebsd-current@freebsd.org Subject: Re: Following vm_lowmem event handler for dirhash 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: Sat, 20 Jun 2009 16:13:31 -0000 On Fri, Jun 19, 2009 at 09:46:40AM +0200, Kamigishi Rei wrote: > Hello, hope you're having a nice day, > > Following > http://lists.freebsd.org/pipermail/freebsd-current/2009-May/007367.html > > > It adds a vm_lowmem event handler to the dirhash code in UFS2 > > so that dirhashes will be deleted when the system is low on memory. > From what I gather, this patch is in -CURRENT now; I've updated to > -CURRENT 3 days ago (after using a snapshot from May) and my previously > stable system threw a kernel panic yesterday. Panic happened during a > benchmark on my ZFS pool (bonnie++ -s 32768) supposedly because of that > exact patch (because ZFS is known to eat a lot of kmem and vm_lowmem was > probably triggered). Alas, I don't have a dump available (because my > system boots from a geom mirror and the swap space is there as well), so > I only have the panic message: "dirhash: NULL hash on list". You probably don't have the latest changes made to dirhash, which I committed in r194387 on the 17th of June. That fixed some problems introduced in my first commit with the vm_lowmem handler for dirhash a couple of weeks ago. Until this latest commit, it is possible that ufsdirhash_destroy(), which is where your "dirhash: NULL hash on list" message comes from, might be trying to destroy an already deleted dirhash. Please try updating your sources and build a new kernel to see if this problem comes up again. Nick > My system is a Core2 Duo on a Q35 motherboard, using 2GB RAM and 4x > 500GB drives, of which 2 are in a GEOM_MIRROR and the other 2 are in a > zpool. > > fujibayashi@ameagari ~ % uname -a > FreeBSD ameagari.fujibayashi.jp 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Tue > Jun 16 21:50:53 JST 2009 > root@ameagari.fujibayashi.jp:/usr/obj/usr/src/sys/Ameagari amd64 > > (Last line in /usr/src/UPDATING states "20090613".) > > -- > Kamigishi Rei > Systems Administrator > WIDE > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"