From owner-freebsd-fs@FreeBSD.ORG Thu May 10 16:44:57 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F0E2016A400 for ; Thu, 10 May 2007 16:44:57 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from mail.bitblocks.com (ns1.bitblocks.com [64.142.15.60]) by mx1.freebsd.org (Postfix) with ESMTP id DDDEF13C457 for ; Thu, 10 May 2007 16:44:57 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost.bitblocks.com [127.0.0.1]) by mail.bitblocks.com (Postfix) with ESMTP id 7FCA35B5A for ; Thu, 10 May 2007 09:44:57 -0700 (PDT) To: freebsd-fs@freebsd.org Date: Thu, 10 May 2007 09:44:57 -0700 From: Bakul Shah Message-Id: <20070510164457.7FCA35B5A@mail.bitblocks.com> Subject: zfs and kmem_map too small panic 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, 10 May 2007 16:44:58 -0000 I still see this panic even after reducing kern.maxvfs to 75000 (and even compling in a limit of 75000). Trying to rsync the freebsd cvs repo from a UFS disk to ZFS triggers it every time. Is anyone else seeing this problem? If so, what is your configuration? I am running -current on an X2 Dual core opteron system but in 32 bit mode. If you are running a similar system but do not run into this bug, did you have to change any default parameters for zfs or the amount of KVM? Thanks!