From owner-freebsd-fs@FreeBSD.ORG  Tue Aug 20 18:28:51 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 E38CADC3;
 Tue, 20 Aug 2013 18:28:50 +0000 (UTC)
 (envelope-from joh.hendriks@gmail.com)
Received: from mail-ve0-x234.google.com (mail-ve0-x234.google.com
 [IPv6:2607:f8b0:400c:c01::234])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9248E22F6;
 Tue, 20 Aug 2013 18:28:50 +0000 (UTC)
Received: by mail-ve0-f180.google.com with SMTP id pb11so631791veb.11
 for <multiple recipients>; Tue, 20 Aug 2013 11:28:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=TPND7HmzGcMUy4Z/bObD6hg3UiPlxDvu4fEps9XZORc=;
 b=iGwZLSnIDqelBz63xMFbhwXVaagS5pZW5Uql4JNAY0OftR8+1LqUMPK1e2QZxDnK/j
 pW8yrTaqPuO6TGOlYCFE9vOtyMvcv/HCMi7ub4upq7LmyIiyjRy1Lt4i3/mATmTFXmEv
 YRQ0NGNu2WUqPL4zN/BtiZMln1bxiO1S1Ry7njTArX454PjCtpDtrWRTiiLMFuSXOFKX
 DPz/dpVZH9G+isqcK9wYLOJ2Qj5IkInk4qYSUOuOP1UnUwl9UxVQ6fFS9EofZe+CTyar
 Ma4/52NvaXBA80AZDf1rQnL3EwdU86GU7Z4imrlMCWQZ6X1me+4TNJ1QzCIkXVRcV5Zj
 /YFQ==
MIME-Version: 1.0
X-Received: by 10.58.106.82 with SMTP id gs18mr2325840veb.18.1377023329433;
 Tue, 20 Aug 2013 11:28:49 -0700 (PDT)
Received: by 10.58.249.1 with HTTP; Tue, 20 Aug 2013 11:28:49 -0700 (PDT)
In-Reply-To: <1377015858.1450.3.camel@localhost>
References: <1377015858.1450.3.camel@localhost>
Date: Tue, 20 Aug 2013 20:28:49 +0200
Message-ID: <CAOaKuAVuJXf-Ceuh0Z4ToLtCc2D+BTVEabcVNWK=vktKjqoQcQ@mail.gmail.com>
Subject: Re: How do we clear a bogus zpool?
From: Johan Hendriks <joh.hendriks@gmail.com>
To: "sbruno@freebsd.org" <sbruno@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
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 18:28:51 -0000

Op dinsdag 20 augustus 2013 schreef Sean Bruno (sean_bruno@yahoo.com):

> I've managed to create a situation where I have a completely bogus zpool
> showing up on my system.  There seems to be no way to wipe this out?
>
> # zpool import
>    pool: zroot
>      id: 854190767471294680
>   state: UNAVAIL
>  status: One or more devices are missing from the system.
>  action: The pool cannot be imported. Attach the missing
>         devices and try again.
>    see: http://illumos.org/msg/ZFS-8000-3C
>  config:
>
>         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
>
>
> Sean
>
>
There is a label clear option for zpool
# zpool labelclear devicename
It will wipe ALL labels, and not only zpool/zfs labels.

Gr
Johan