From owner-freebsd-fs@FreeBSD.ORG  Tue Aug 20 23:40:21 2013
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 57EC9FFC;
 Tue, 20 Aug 2013 23:40:21 +0000 (UTC)
 (envelope-from wblock@wonkity.com)
Received: from wonkity.com (wonkity.com [67.158.26.137])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 0AEB32449;
 Tue, 20 Aug 2013 23:40:20 +0000 (UTC)
Received: from wonkity.com (localhost [127.0.0.1])
 by wonkity.com (8.14.7/8.14.7) with ESMTP id r7KNeJmJ000687;
 Tue, 20 Aug 2013 17:40:19 -0600 (MDT)
 (envelope-from wblock@wonkity.com)
Received: from localhost (wblock@localhost)
 by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r7KNeJXt000684;
 Tue, 20 Aug 2013 17:40:19 -0600 (MDT)
 (envelope-from wblock@wonkity.com)
Date: Tue, 20 Aug 2013 17:40:19 -0600 (MDT)
From: Warren Block <wblock@wonkity.com>
To: sbruno@freebsd.org
Subject: Re: How do we clear a bogus zpool?
In-Reply-To: <1377026426.1478.2.camel@localhost>
Message-ID: <alpine.BSF.2.00.1308201730220.99980@wonkity.com>
References: <1377015858.1450.3.camel@localhost>
 <CAOFF+Z2gA6KxLwZNb7Zyduy3f+-YtfOFbyUO6RaDOexo0X_n_g@mail.gmail.com>
 <1377026426.1478.2.camel@localhost>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (wonkity.com [127.0.0.1]); Tue, 20 Aug 2013 17:40:19 -0600 (MDT)
Cc: freebsd-fs <freebsd-fs@freebsd.org>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Tue, 20 Aug 2013 23:40:21 -0000

On Tue, 20 Aug 2013, Sean Bruno wrote:

> On Tue, 2013-08-20 at 12:41 -0400, Sam Fourman Jr. wrote:
>>>         zroot                     UNAVAIL  insufficient replicas
>>>           raidz1-0                UNAVAIL  insufficient replicas
>>>             17925463268209287656  UNAVAIL  cannot open
>>>             11020448220822113890  UNAVAIL  corrupted data
>>>             10143858893287711942  UNAVAIL  corrupted data
>>>             7542790596970715955   UNAVAIL  corrupted data
>>>             10811885036534933813  UNAVAIL  corrupted data
>>>             13343774937261906429  UNAVAIL  corrupted data
>>>
>>> # zpool destroy -f zroot
>>> cannot open 'zroot': no such pool
>>> # zpool clear -F zroot
>>> cannot open 'zroot': no such pool
>>>
>> gpart -F destroy /dev/adX
>
> Sure.  But, what device to destroy?  Its not clear from the zpool list
> where the "pool" is coming from.

gpart probably won't be able to recognize ZFS metadata and clear it. 
Would be kind of handy, though.

The man page for 'zpool labelclear' says it takes a device for a 
parameter.  But the device must not be part of a pool...

If all else fails, using dd to erase the first and last couple of 
megabytes of each of the disks ought to clear it.  (Untested...)