From owner-freebsd-fs@FreeBSD.ORG Thu Jan 21 18:34:16 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 57E231065672 for ; Thu, 21 Jan 2010 18:34:16 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id EC1128FC18 for ; Thu, 21 Jan 2010 18:34:15 +0000 (UTC) Received: from [10.8.0.2] (remotevpn [10.8.0.2]) by ns1.feral.com (8.14.3/8.14.3) with ESMTP id o0LIYDW0096132 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 21 Jan 2010 10:34:14 -0800 (PST) (envelope-from mj@feral.com) Message-ID: <4B589E25.3010608@feral.com> Date: Thu, 21 Jan 2010 10:34:13 -0800 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091209 Fedora/3.0-3.fc11 Thunderbird/3.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.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 X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.2.3 (ns1.feral.com [10.8.0.1]); Thu, 21 Jan 2010 10:34:14 -0800 (PST) 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 Reply-To: mj@feral.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jan 2010 18:34:16 -0000 Can you get a stack traceback? > 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. > >