From owner-freebsd-current@FreeBSD.ORG Fri Apr 27 23:39:29 2007 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CC30016A400 for ; Fri, 27 Apr 2007 23:39:29 +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 B6F9D13C448 for ; Fri, 27 Apr 2007 23:39:29 +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 361EA5B29; Fri, 27 Apr 2007 16:18:55 -0700 (PDT) To: Gary Jennejohn In-reply-to: Your message of "Fri, 27 Apr 2007 20:18:59 +0200." <200704271818.l3RIIxBw028908@peedub.jennejohn.org> Date: Fri, 27 Apr 2007 16:18:55 -0700 From: Bakul Shah Message-Id: <20070427231855.361EA5B29@mail.bitblocks.com> Cc: current@FreeBSD.org Subject: Re: help with latest version of ZFS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Apr 2007 23:39:29 -0000 I reported this yesterday on freebsd-fs. Reducing kern.maxvnodes to about 3/4th its current value gets rid of this panic. See Pawel's response to my message on freebsd-fs list (assuming it has shown up by now).