From owner-freebsd-current@FreeBSD.ORG Sat Jun 20 13:03:50 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 9B1E51065672 for ; Sat, 20 Jun 2009 13:03:50 +0000 (UTC) (envelope-from spambox@haruhiism.net) Received: from fujibayashi.jp (karas.fujibayashi.jp [77.221.159.4]) by mx1.freebsd.org (Postfix) with ESMTP id 56E1D8FC08 for ; Sat, 20 Jun 2009 13:03:50 +0000 (UTC) (envelope-from spambox@haruhiism.net) Received: from [192.168.0.10] (datacenter.telecombusinessconsulting.net [77.221.137.211]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by fujibayashi.jp (Postfix) with ESMTPSA id 0738E78F86 for ; Fri, 19 Jun 2009 11:46:32 +0400 (MSD) Message-ID: <4A3B4260.6070200@haruhiism.net> Date: Fri, 19 Jun 2009 11:46:40 +0400 From: Kamigishi Rei User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 20 Jun 2009 13:15:32 +0000 Subject: 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 13:03:50 -0000 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". 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