From owner-freebsd-current@FreeBSD.ORG Sun Jan 6 22:14:16 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 3242416A41A for ; Sun, 6 Jan 2008 22:14:16 +0000 (UTC) (envelope-from ender@enderzone.com) Received: from www.ksdhost.com (www.ksdhost.com [75.126.66.82]) by mx1.freebsd.org (Postfix) with ESMTP id 093B013C459 for ; Sun, 6 Jan 2008 22:14:15 +0000 (UTC) (envelope-from ender@enderzone.com) Received: (qmail 92568 invoked from network); 6 Jan 2008 15:47:34 -0600 Received: from buff-broadband-ws-86.dsl.pwrtc.com (HELO ?192.168.5.100?) (64.184.124.87) by www.ksdhost.com with SMTP; 6 Jan 2008 15:47:34 -0600 Message-ID: <47814C4F.7050206@enderzone.com> Date: Sun, 06 Jan 2008 16:46:55 -0500 From: Ender User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Ivan Voras References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: ZFS on AMD64 - any recent crashes? 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: Sun, 06 Jan 2008 22:14:16 -0000 Ivan Voras wrote: > Hi, > > In light of the recent discussion about ZFS stability, does anyone > still have kmem_map_too_small panics on AMD64 after tuning it (as > presented in http://wiki.freebsd.org/ZFSTuningGuide)? > > I'm interested in reports like this: > http://kerneltrap.org/mailarchive/freebsd-current/2007/9/21/271557 > (note that this report is for an untuned system). > > > > I have vm.kmem_size="1073741824" I used to have vm.kmem_size_max=1073741824 as well but heard it was not needed to have both. (it made no change) I never see my vfs.numvnodes over 60,000 but i have the limit at 400,000 anyways amd64 freebsd FreeBSD 7.0-BETA4 #0: Sat Dec 15 06:40:09 EST 2007 graff@nfsd.com:/usr/obj/usr/src/sys/NFSD Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Dual-Core AMD Opteron(tm) Processor 2218 (2593.52-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x40f12 Stepping = 2 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x1f Cores per package: 2 usable memory = 8580689920 (8183 MB) avail memory = 8257769472 (7875 MB) ACPI APIC Table: <091107 APIC1523> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs All this server does is run nfsd, no apache, no mysql, no rsync, no zfs snapshots either. Jan 1 15:48:09 nfsd kernel: ZFS filesystem version 6 Jan 1 15:48:09 nfsd kernel: ZFS storage pool version 6 Jan 1 15:48:09 nfsd savecore: reboot after panic: kmem_malloc(131072): kmem_map too small: 864546816 total allocated In fact i was going to paste the zpool status here, but typing it in caused the server to crash. In short i have 4 drives paired in 2 mirrors, for a raid 0 + 1 effect, normal SATA drives directly connected to zfs. I have tested this hardware thoroughly without zfs, memory test, make buildworld tests, etc so i know it is stable hardware. I hate to report bad news but i hope this leads to a fix