From owner-freebsd-fs@FreeBSD.ORG Fri Oct 5 00:01:02 2007 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 31C3C16A468; Fri, 5 Oct 2007 00:01:02 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id C5FF113C4B7; Fri, 5 Oct 2007 00:01:01 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id A541F45F44; Fri, 5 Oct 2007 02:01:00 +0200 (CEST) Received: from localhost (154.81.datacomsa.pl [195.34.81.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 3F52E456AB; Fri, 5 Oct 2007 02:00:55 +0200 (CEST) Date: Fri, 5 Oct 2007 02:00:46 +0200 From: Pawel Jakub Dawidek To: freebsd-fs@FreeBSD.org Message-ID: <20071005000046.GC92272@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bKyqfOwhbdpXa4YI" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-current@FreeBSD.org Subject: ZFS kmem_map too small. 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: Fri, 05 Oct 2007 00:01:02 -0000 --bKyqfOwhbdpXa4YI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi. We'are about to branch RELENG_7 and I'd like to start discussion with folks that experience 'kmem_map too small' panic with the latest HEAD. I'm trying hard to reproduce it and I can't, so I need to gather more info how you are able to provoke this panic. What I did was to rsync 200 FreeBSD src trees from one directory to another on the same ZFS file system. It worked fine. The system I'm using is i386 and the only tuning I did is bigger kmem_map. From my /boot/loader.conf: vm.kmem_size=3D629145600 vm.kmem_size_max=3D629145600 The machine is dual core Pentium D 3GHz with 1GB of RAM. My pool is: lcf:root:/tank/0# zpool status pool: tank state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 ad4 ONLINE 0 0 0 ad5 ONLINE 0 0 0 ad6 ONLINE 0 0 0 ad7 ONLINE 0 0 0 errors: No known data errors If you can still see those panic, please let me know as soon as possible and try to describe what your workload looks like, how to reproduce it, etc. I'd really like ZFS to be rock-stable for 7.0 even on i386. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --bKyqfOwhbdpXa4YI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHBX6uForvXbEpPzQRAnb3AJ9Qa9S4pmIeA1RRbfq/f8krB/jTQACgsjBL PJp2ZwshSM4CPetRugv6Id8= =ONnA -----END PGP SIGNATURE----- --bKyqfOwhbdpXa4YI--