From owner-freebsd-stable@FreeBSD.ORG Sat Jul 19 10:51:06 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 B95E41065674 for ; Sat, 19 Jul 2008 10:51:06 +0000 (UTC) (envelope-from daniel_k_eriksson@telia.com) Received: from pne-smtpout1-sn2.hy.skanova.net (pne-smtpout1-sn2.hy.skanova.net [81.228.8.83]) by mx1.freebsd.org (Postfix) with ESMTP id 5BF9C8FC14 for ; Sat, 19 Jul 2008 10:51:06 +0000 (UTC) (envelope-from daniel_k_eriksson@telia.com) Received: from royal64.emp.zapto.org (195.198.193.168) by pne-smtpout1-sn2.hy.skanova.net (7.3.129) id 4873C9830020F462; Sat, 19 Jul 2008 12:50:51 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-class: urn:content-classes:message Date: Sat, 19 Jul 2008 12:50:50 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7235.2 Message-ID: <4F9C9299A10AE74E89EA580D14AA10A61A197B@royal64.emp.zapto.org> In-Reply-To: <1216459022.6521.6.camel@porksoda> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Panic on ZFS startup after crash Thread-Index: AcjpgE9bRaz+C87STpyvImgi/65+SgADEnyw References: <4F9C9299A10AE74E89EA580D14AA10A61A197A@royal64.emp.zapto.org> <1216459022.6521.6.camel@porksoda> From: "Daniel Eriksson" To: "freebsd-stable" Cc: Alex Trull 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: Sat, 19 Jul 2008 10:51:06 -0000 Alex Trull wrote: > I've tried neither of these in your particular case, but they might be > worth a try: >=20 > Just a suggestion, but try specify vfs.zfs.zil_disable=3D1 or=20 > as a kernel > variable in the boot cli. >=20 > You may want to try export and import the pool and see how it likes it > then. I considered disabling the zil but didn't think it would make a difference (because zfs will most likely check if there is any data in zil on startup anyway). I'll try it though! Importing the pool results in the exact same problem. (I couldn't export the live pool because the box paniced, but by making sure the vdev was unavailable on zfs startup I could export the stale pool, enable the vdev (by doing a "geli attach") and then I tried to import the pool. No luck, same panic message. ___ Daniel Eriksson (http://www.toomuchdata.com/)