From owner-freebsd-fs@FreeBSD.ORG  Fri Nov  6 23:02:27 2009
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 68901106566C
	for <freebsd-fs@freebsd.org>; Fri,  6 Nov 2009 23:02:27 +0000 (UTC)
	(envelope-from james-freebsd-fs2@jrv.org)
Received: from mail.jrv.org (adsl-70-243-84-13.dsl.austtx.swbell.net
	[70.243.84.13]) by mx1.freebsd.org (Postfix) with ESMTP id E24BF8FC0A
	for <freebsd-fs@freebsd.org>; Fri,  6 Nov 2009 23:02:26 +0000 (UTC)
Received: from kremvax.housenet.jrv (kremvax.housenet.jrv [192.168.3.124])
	by mail.jrv.org (8.14.3/8.14.3) with ESMTP id nA6N2Nhe037117;
	Fri, 6 Nov 2009 17:02:24 -0600 (CST)
	(envelope-from james-freebsd-fs2@jrv.org)
Authentication-Results: mail.jrv.org; domainkeys=pass (testing)
	header.from=james-freebsd-fs2@jrv.org
DomainKey-Signature: a=rsa-sha1; s=enigma; d=jrv.org; c=nofws; q=dns;
	h=message-id:date:from:user-agent:mime-version:to:cc:subject:
	references:in-reply-to:content-type:content-transfer-encoding;
	b=JNskFQDLotR+FX/5Ffzjgd/GoyHiaBt+/BhIQNrJjYOoP4EWQAby2kW2XWQlBq7HE
	z0qEr1aZd8DA7Ds9gk9Y+CMImNHOgfIP2RPawrekVjfhjnXI0fL6QOB2PCV2xtvp+cz
	94HgP3ifGs0plonm4PmLQF7nnrD4N30xkIKNyjY=
Message-ID: <4AF4AAFF.2080104@jrv.org>
Date: Fri, 06 Nov 2009 17:02:23 -0600
From: "James R. Van Artsdalen" <james-freebsd-fs2@jrv.org>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Gerrit_K=FChn?= <gerrit@pmp.uni-hannover.de>
References: <20091106094734.4b056899.gerrit@pmp.uni-hannover.de>	<4AF4123A.4080301@andric.com>
	<20091106231440.4f0f2cbb.gerrit@pmp.uni-hannover.de>
In-Reply-To: <20091106231440.4f0f2cbb.gerrit@pmp.uni-hannover.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-fs@freebsd.org
Subject: Re: 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 <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Nov 2009 23:02:27 -0000

Gerrit K=FChn wrote:
> 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 sam=
e
> panic):

You may be able to recover your pool by changing the line below, but I
have never tried it: it may clobber the pool.  You definitely don't want
this change normally!  It may be necessary to avoid calling zil_destroy
here too.

How the ZIL got corrupted - if it did - is a harder question.  What kind
of hard disk is this, and how is it connected to the system?  Was there
any redundancy (mirror, raidz)?

void
zil_replay(objset_t *os, void *arg, uint64_t *txgp,
        zil_replay_func_t *replay_func[TX_MAX_TYPE],
        zil_replay_cleaner_t *replay_cleaner)
{
        zilog_t *zilog =3D dmu_objset_zil(os);
        const zil_header_t *zh =3D zilog->zl_header;
        zil_replay_arg_t zr;

=3D=3D>     if (1 || zil_empty(zilog)) {
                zil_destroy(zilog, B_TRUE);
                return;
        }