From owner-freebsd-stable@FreeBSD.ORG Sun Jul 25 20:18:15 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A3C1106567C for ; Sun, 25 Jul 2010 20:18:15 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta10.emeryville.ca.mail.comcast.net (qmta10.emeryville.ca.mail.comcast.net [76.96.30.17]) by mx1.freebsd.org (Postfix) with ESMTP id 9E8A68FC20 for ; Sun, 25 Jul 2010 20:18:15 +0000 (UTC) Received: from omta14.emeryville.ca.mail.comcast.net ([76.96.30.60]) by qmta10.emeryville.ca.mail.comcast.net with comcast id mKek1e0021HpZEsAALJEfv; Sun, 25 Jul 2010 20:18:14 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta14.emeryville.ca.mail.comcast.net with comcast id mLJD1e0093LrwQ28aLJEhD; Sun, 25 Jul 2010 20:18:14 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 3CD459B425; Sun, 25 Jul 2010 13:18:11 -0700 (PDT) Date: Sun, 25 Jul 2010 13:18:11 -0700 From: Jeremy Chadwick To: Dan Langille Message-ID: <20100725201811.GA33611@icarus.home.lan> References: <4C4C7B4A.7010003@langille.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C4C7B4A.7010003@langille.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: stable@freebsd.org Subject: Re: zpool destroy causes panic 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: Sun, 25 Jul 2010 20:18:15 -0000 On Sun, Jul 25, 2010 at 01:58:34PM -0400, Dan Langille wrote: > [...] > NAME STATE READ WRITE CKSUM > storage ONLINE 0 0 0 > raidz2 ONLINE 0 0 0 > gpt/disk01 ONLINE 0 0 0 > gpt/disk02 ONLINE 0 0 0 > gpt/disk03 ONLINE 0 0 0 > gpt/disk04 ONLINE 0 0 0 > gpt/disk05 ONLINE 0 0 0 > /tmp/sparsefile1.img UNAVAIL 0 0 0 corrupted data > /tmp/sparsefile2.img UNAVAIL 0 0 0 corrupted data > > [...] > > Another attempt to destroy the array created a panic. > Suggestions as to how to remove this array and get started again? > > [...] > > FreeBSD kraken.unixathome.org 8.0-STABLE FreeBSD 8.0-STABLE #0: Fri Mar 5 00:46:11 EST 2010 dan@kraken.example.org:/usr/obj/usr/src/sys/KRAKEN amd64 1) Try upgrading the system (to 8.1-STABLE). There have been numerous changes to ZFS on RELENG_8 since March 5th. I don't know if any of them would address your problem. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c#rev1.8.2.4 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c#rev1.8.2.3 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c#rev1.8.2.2 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c#rev1.8.2.1 2) Try bringing the system down into single-user mode and zeroing out the first and last 64kbytes of each gpt/diskXX (you'll have to figure this out on your own, I'm not familiar with GPT) so that the ZFS metadata goes away. Footnote: can someone explain to me how ZFS would, upon reboot, know that /tmp/sparsefile[12].img are part of the pool? How would ZFS taste metadata in this situation? -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |