From owner-freebsd-fs@FreeBSD.ORG  Tue Aug 20 16:41:36 2013
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id D7D699EE;
 Tue, 20 Aug 2013 16:41:36 +0000 (UTC)
 (envelope-from sfourman@gmail.com)
Received: from mail-vc0-x22a.google.com (mail-vc0-x22a.google.com
 [IPv6:2607:f8b0:400c:c03::22a])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 863EF2C5C;
 Tue, 20 Aug 2013 16:41:36 +0000 (UTC)
Received: by mail-vc0-f170.google.com with SMTP id kw10so484705vcb.29
 for <multiple recipients>; Tue, 20 Aug 2013 09:41:35 -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=XOkXJQuq/LN0XMol3P5+ICb+vYV3wweD5Bs4krwlikc=;
 b=IAj9G5rF4yDHeAxpS+R8kGBq2ePTt2xPQJdbdeDK90OzfCMfKPClSpEyqrJdId44ja
 JY552frbmh0+f/UHS89d7V84z3DyI9KsFX4AVULzC5WHQxGsrgSmrczbQlctTPHa7F4F
 LSSPWj37NrDE+hVmzgie5OudQk39nV6WS9/A3GhxhS8p1PxT9dw6qo3MDPCMXwG1345G
 2ENvO/3+4OKb8d1kg+0qb55uLN7gJ0jcedyAEuvT/m0vo28uW4DA552PasCmHUBk4eab
 z0bcxPujEY9rrHm1oV579EtIVB9FTTrJdtdvG+IdDITOWqe/+x/ZR2wP6H+7/St34MyK
 C8iQ==
MIME-Version: 1.0
X-Received: by 10.52.73.162 with SMTP id m2mr1690760vdv.24.1377016895701; Tue,
 20 Aug 2013 09:41:35 -0700 (PDT)
Received: by 10.220.96.78 with HTTP; Tue, 20 Aug 2013 09:41:35 -0700 (PDT)
Received: by 10.220.96.78 with HTTP; Tue, 20 Aug 2013 09:41:35 -0700 (PDT)
In-Reply-To: <1377015858.1450.3.camel@localhost>
References: <1377015858.1450.3.camel@localhost>
Date: Tue, 20 Aug 2013 12:41:35 -0400
Message-ID: <CAOFF+Z2gA6KxLwZNb7Zyduy3f+-YtfOFbyUO6RaDOexo0X_n_g@mail.gmail.com>
Subject: Re: How do we clear a bogus zpool?
From: "Sam Fourman Jr." <sfourman@gmail.com>
To: 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 16:41:37 -0000

On Aug 20, 2013 12:37 PM, "Sean Bruno" <sean_bruno@yahoo.com> wrote:
>
> 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
>
gpart -F destroy /dev/adX

> Sean
>