From owner-freebsd-fs@FreeBSD.ORG  Wed Nov  7 13:49:10 2012
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id 3F888E3E
 for <freebsd-fs@freebsd.org>; Wed,  7 Nov 2012 13:49:10 +0000 (UTC)
 (envelope-from joh.hendriks@gmail.com)
Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com
 [209.85.214.54])
 by mx1.freebsd.org (Postfix) with ESMTP id B7AFE8FC1A
 for <freebsd-fs@freebsd.org>; Wed,  7 Nov 2012 13:49:09 +0000 (UTC)
Received: by mail-bk0-f54.google.com with SMTP id jf20so829524bkc.13
 for <freebsd-fs@freebsd.org>; Wed, 07 Nov 2012 05:49:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=message-id:date:from:user-agent:mime-version:to:cc:subject
 :references:in-reply-to:content-type:content-transfer-encoding;
 bh=pXh9VLDXljlmp5EWuhJC7hnDvjU9HnXXR0gSNminA1U=;
 b=v4JAuwxcgk6LxDN1BD7tcNjE9+b7H4uEtla71A1wUOtdJf0sfiOehMAtTrKWNzNHem
 eEyQKJQVtAqPv0OanHh5Or7+UtSrzrj1YkGWl57vllzh/tNKGGWS8lf2jBMsv0MA3fKf
 pwXLgjKHjcNdw6W1RWbnm9/9Jb5IAIYf9SViX4+NuYnzxhWQ+rmHMLhLzITpinwqgh0R
 gm1HVO2WDUYA8KUek94zEWPfcBslIn36A9sD5GIU2rI1NE5ng/NIJE2Xslql+5GKoAPw
 N43OZZ2+dQT9R+YKMHzPCLzMySi3tnatH9kj2etOrxtqeLkwAvnzIzmqcMk5Ht9j6Azv
 TICw==
Received: by 10.204.147.5 with SMTP id j5mr1180193bkv.21.1352296148803;
 Wed, 07 Nov 2012 05:49:08 -0800 (PST)
Received: from [192.168.50.105] (double-l.xs4all.nl. [80.126.205.144])
 by mx.google.com with ESMTPS id k21sm14513043bkv.1.2012.11.07.05.49.07
 (version=SSLv3 cipher=OTHER); Wed, 07 Nov 2012 05:49:07 -0800 (PST)
Message-ID: <509A66D2.5060706@gmail.com>
Date: Wed, 07 Nov 2012 14:49:06 +0100
From: Johan Hendriks <joh.hendriks@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Beeblebrox <zaphod@berentweb.com>
Subject: Re: [ZFS] How to fix corrupt ZDB
References: <1352294866076-5758864.post@n5.nabble.com>
In-Reply-To: <1352294866076-5758864.post@n5.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 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: Wed, 07 Nov 2012 13:49:10 -0000

Beeblebrox schreef:
> I removed the HDD before deleting one of the zpools, then I added a ZIL
> device using gnop. Now I get multiple ashift values even though I have only
> 1 zpool (vdev):
> zdb mypool | grep ashift
> ashift: 9
> ashift: 12
> ashift: 9
> ashift: 12
>
> Looking through various ZDB functions has shown me that the previously
> removed pool is still in ZDB. But unfortunately the ZDB manual talks more
> about "status reporting" and not much about "error correction".
>
> Any ideas on how to correct/remove/delete faulty ZDB entries (other than
> re-install)?
>
Can you show the output of zpool status.

gr
johan