From owner-freebsd-stable@FreeBSD.ORG Mon Jul 21 13:49:27 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3148F106566B; Mon, 21 Jul 2008 13:49:27 +0000 (UTC) (envelope-from daniel_k_eriksson@telia.com) Received: from pne-smtpout2-sn1.fre.skanova.net (pne-smtpout2-sn1.fre.skanova.net [81.228.11.159]) by mx1.freebsd.org (Postfix) with ESMTP id D02D98FC19; Mon, 21 Jul 2008 13:49:26 +0000 (UTC) (envelope-from daniel_k_eriksson@telia.com) Received: from royal64.emp.zapto.org (195.198.193.168) by pne-smtpout2-sn1.fre.skanova.net (7.3.129) id 4843FAEB009AC52A; Mon, 21 Jul 2008 15:49:25 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-class: urn:content-classes:message Date: Mon, 21 Jul 2008 15:49:24 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7235.2 Message-ID: <4F9C9299A10AE74E89EA580D14AA10A61A197F@royal64.emp.zapto.org> In-Reply-To: <20080721090235.GA2953@garage.freebsd.pl> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Panic on ZFS startup after crash Thread-Index: AcjrEMumyrEYBtvwSkq8gGV+vg0W2AAJjvLQ References: <4F9C9299A10AE74E89EA580D14AA10A61A197A@royal64.emp.zapto.org> <20080719221813.GC4733@garage.freebsd.pl> <4F9C9299A10AE74E89EA580D14AA10A61A197E@royal64.emp.zapto.org> <20080721090235.GA2953@garage.freebsd.pl> From: "Daniel Eriksson" To: Cc: Pawel Jakub Dawidek Subject: RE: Panic on ZFS startup after crash X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2008 13:49:27 -0000 Pawel Jakub Dawidek wrote: > I'm afraid your pool's metadata is > somehow corrupted that ZFS can't handle that. Yes, that's my conclusion also. It looks like the intent log is messed up enough to trigger an assert while ZFS tries to parse/replay it. > I saw warnings in your > first e-mail about ZFS not beeing able to replay ZIL. Can you try > disabling ZIL? Something like: I've already tried this, and it made no difference. When the box crashed ZIL was enabled, and for some reason garbage got written into the ZIL. Now whenever ZFS tries to import the pool it sees a non-empty ZIL and tries to parse/replay it. Is there an easy way to trick ZFS into thinking the ZIL is empty? > Although I'm not sure if disabling ZIL will prevent replaying=20 > previously prepared ZIL. It won't unfortunately. > If that won't help, I'm afraid the last suggestion I can > provide is to try the lastest ZFS version (I can prepare a=20 > patch for you in a few days). I could probably prepare a temporary install of 8-CURRENT on a spare drive and boot from that if it's easier for you to make a patch against CURRENT instead of RELENG_7_0. > You could also try=20 > to import a pool read-only, but I just tried doing so with > 'zpool import -o ro ' command and it mount file systems > read-write. Not sure why it doesn't work, but I'll try to fix=20 > it today. I'll try that! ___ Daniel Eriksson (http://www.toomuchdata.com/)