From owner-freebsd-fs@FreeBSD.ORG Thu Jan 21 18:25:13 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76D7D106568F for ; Thu, 21 Jan 2010 18:25:13 +0000 (UTC) (envelope-from doug@polands.org) Received: from hrndva-omtalb.mail.rr.com (hrndva-omtalb.mail.rr.com [71.74.56.122]) by mx1.freebsd.org (Postfix) with ESMTP id 32DAE8FC16 for ; Thu, 21 Jan 2010 18:25:12 +0000 (UTC) Received: from hrndva-omtalb.mail.rr.com ([10.128.143.53]) by hrndva-qmta04.mail.rr.com with ESMTP id <20100121180645097.VVRG22884@hrndva-qmta04.mail.rr.com> for ; Thu, 21 Jan 2010 18:06:45 +0000 X-Authority-Analysis: v=1.0 c=1 a=zE3mbNJvjOkA:10 a=370Rr2IVWakicQaKVlIA:9 a=-8jeenipcSc8JWl-pzubFp3jUpQA:4 X-Cloudmark-Score: 0 X-Originating-IP: 75.87.219.217 Received: from [75.87.219.217] ([75.87.219.217:52446] helo=haran.polands.org) by hrndva-oedge03.mail.rr.com (envelope-from ) (ecelerity 2.2.2.39 r()) with ESMTP id 9E/D4-05903-F67985B4; Thu, 21 Jan 2010 18:05:35 +0000 Received: from [172.16.1.37] (sichem-wifi.polands.org [172.16.1.37]) by haran.polands.org (8.14.3/8.14.3) with ESMTP id o0LI5YGC026970 for ; Thu, 21 Jan 2010 12:05:34 -0600 (CST) (envelope-from doug@polands.org) Message-ID: <4B58976E.1020402@polands.org> Date: Thu, 21 Jan 2010 12:05:34 -0600 From: Doug Poland User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Repeatable ZFS "kmem map too small" panic on 8.0-STABLE X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jan 2010 18:25:13 -0000 Hello, I've got an 8.0-STABLE (amd64) box with 4GB RAM. The machine is running off a 6-disk RAIDZ1 booting from GPT. The box consistently panics on unixbench's fsdisk program. I have been gathering some metrics in an attempt to isolate the parameters that are significant, but I admit I do not really understand all the relationships. At this point, I have nothing set in /boot/loader.conf Here are some of the values I was recording within seconds of the panic: # dmesg | grep memory real memory = 4294967296 (4096 MB) avail memory = 3961372672 (3777 MB) kstat.zfs.misc.arcstats.size: 308522248 vfs.zfs.arc_max: 829480960 vfs.zfs.arc_meta_limit: 207370240 vfs.zfs.arc_meta_used: 165575944 vfs.zfs.arc_min: 103685120 vm.kmem_size: 1327169536 vm.kmem_size_max: 329853485875 # vmstat -m | egrep 'InUse|solaris' Type InUse MemUse HighUse solaris 491349 1316172K - % zpool status pool: bethesda state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM bethesda ONLINE 0 0 0 raidz1 ONLINE 0 0 0 gpt/disk0 ONLINE 0 0 0 gpt/disk1 ONLINE 0 0 0 gpt/disk2 ONLINE 0 0 0 gpt/disk3 ONLINE 0 0 0 gpt/disk4 ONLINE 0 0 0 gpt/disk5 ONLINE 0 0 0 errors: No known data errors My concern is if I can panic the box with a simple file system benchmark, what will happen when I rysnc files across a 1GB LAN connection? I am very willing to run any number of tests and tweek ZFS as necessary. Please advise. -- Regards, Doug