From owner-freebsd-fs@FreeBSD.ORG Fri Nov 6 22:14:45 2009 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 E0F701065672 for ; Fri, 6 Nov 2009 22:14:45 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106]) by mx1.freebsd.org (Postfix) with ESMTP id 5167F8FC12 for ; Fri, 6 Nov 2009 22:14:44 +0000 (UTC) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id nA6MEfbp002808; Fri, 6 Nov 2009 23:14:43 +0100 Received: from pmp.uni-hannover.de (theq.pmp.uni-hannover.de [130.75.117.4]) by www.pmp.uni-hannover.de (Postfix) with SMTP id 6E39524; Fri, 6 Nov 2009 23:14:41 +0100 (CET) Date: Fri, 6 Nov 2009 23:14:40 +0100 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: Dimitry Andric Message-Id: <20091106231440.4f0f2cbb.gerrit@pmp.uni-hannover.de> In-Reply-To: <4AF4123A.4080301@andric.com> References: <20091106094734.4b056899.gerrit@pmp.uni-hannover.de> <4AF4123A.4080301@andric.com> Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?= Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover) X-Mailer: Sylpheed 2.4.2 (GTK+ 2.10.12; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-PMX-Version: 5.5.5.374460, Antispam-Engine: 2.7.1.369594, Antispam-Data: 2009.11.6.220033 Cc: freebsd-fs@freebsd.org Subject: trace for zfs panic mounting fs after crash with RC2 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, 06 Nov 2009 22:14:46 -0000 On Fri, 06 Nov 2009 13:10:34 +0100 Dimitry Andric wrote about Re: zfs panic mounting fs after crash with RC2: DA> On 2009-11-06 09:47, Gerrit K=FChn wrote: DA> > unfortunately I got no answer concerning this problem so far on DA> > -stable and -current (apart from the suggestion to try it again DA> > here :-). I can reproduce the panic, and if someone can guide me DA> > what to do with kdb, gdb, zdb or whatever tool might be needed to DA> > get the information needed to fix this, I'm all ears... DA> At least a backtrace would be nice. :) I recomplied the kernel with ddb support and got the following trace (using mount -t zfs instead of zfs mount this time, but getting the same panic): I have the system still sitting at this point and can also 100% reproduce the panic. Please let me know if (and how) any further information can get pulled out of the debugger. cu Gerrit