From owner-freebsd-fs@FreeBSD.ORG Thu Jan 21 19:06:04 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 E1C12106568D for ; Thu, 21 Jan 2010 19:06:04 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mx.egr.msu.edu (surfnturf.egr.msu.edu [35.9.37.164]) by mx1.freebsd.org (Postfix) with ESMTP id B34488FC08 for ; Thu, 21 Jan 2010 19:06:04 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mx.egr.msu.edu (Postfix) with ESMTP id 3FE6CEE47D; Thu, 21 Jan 2010 13:43:54 -0500 (EST) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mx.egr.msu.edu ([127.0.0.1]) by localhost (surfnturf.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TMYxvJwxKnoD; Thu, 21 Jan 2010 13:43:54 -0500 (EST) Received: from [35.9.44.65] (daemon.egr.msu.edu [35.9.44.65]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mcdouga9) by mx.egr.msu.edu (Postfix) with ESMTPSA id F3E50EE47A; Thu, 21 Jan 2010 13:43:53 -0500 (EST) Message-ID: <4B58A069.8000802@egr.msu.edu> Date: Thu, 21 Jan 2010 13:43:53 -0500 From: Adam McDougall User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.5) Gecko/20100103 Thunderbird/3.0 MIME-Version: 1.0 To: doug@polands.org References: <4B58976E.1020402@polands.org> In-Reply-To: <4B58976E.1020402@polands.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: 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 19:06:05 -0000 Put this in /boot/loader.conf: vm.kmem_size="20G" It is intentionally higher than your amount of ram. On 01/21/10 13:05, Doug Poland wrote: > 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. > >