From owner-freebsd-current@FreeBSD.ORG Wed Jul 24 06:22:29 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DBB747AC for ; Wed, 24 Jul 2013 06:22:28 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9E2F92BB1 for ; Wed, 24 Jul 2013 06:22:28 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.80.1) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1V1sSp-000l4V-Sh>; Wed, 24 Jul 2013 08:22:19 +0200 Received: from e179070139.adsl.alicedsl.de ([85.179.70.139] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.80.1) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1V1sSp-001xUp-Nw>; Wed, 24 Jul 2013 08:22:19 +0200 Date: Wed, 24 Jul 2013 08:22:14 +0200 From: "O. Hartmann" To: FreeBSD CURRENT Subject: ZPOOL import failure due to multiple pool IDs? Message-ID: <20130724082214.3168b664@thor.walstatt.dyndns.org> Organization: FU Berlin X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/z9kSIl0Em4M+oyfKrrubaOh"; protocol="application/pgp-signature" X-Originating-IP: 85.179.70.139 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jul 2013 06:22:29 -0000 --Sig_/z9kSIl0Em4M+oyfKrrubaOh Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I have trouble with a ZFS pool after interrupted scrubbing on FreeBSD 10-CURREN (10.0-CURRENT #1 r253579: Tue Jul 23 20:31:59 CEST 2013 amd64). After I shut down the box while the ZFS pool in question was still in scrubbing, after a reboot the system marked that pool as defect. I tried to clean the reported data corruption by adding the -F flag to the import, but surprisingly, the pool has ambigious IDs confusing the system (and me): pool: BACKUP00 id: 257822624560506537 state: FAULTED status: The pool metadata is corrupted. action: The pool cannot be imported due to damaged devices or data. The pool may be active on another system, but can be imported using the '-f' flag. see: http://illumos.org/msg/ZFS-8000-72 config: BACKUP00 FAULTED corrupted data ada3p1 ONLINE pool: BACKUP00 id: 9337833315545958689 state: FAULTED status: One or more devices contains corrupted data. action: The pool cannot be imported due to damaged devices or data. The pool may be active on another system, but can be imported using the '-f' flag. see: http://illumos.org/msg/ZFS-8000-5E config: BACKUP00 FAULTED corrupted data 8544670861382329237 UNAVAIL corrupted data I do not know what happens here. The pool has been upgraded twice as far as I remember, since the disk/device is used as a compressed backup device and only used for that purpose. But for a couple of time now with FreeBSD 10, it starts to fail when the scrubbing is interrupted by a shutdown. I remember that scrubbing of pools sesumed after the next reboot - but I realised that this seems to be a problem now for some reason on FreeBSD 10. I had a situation like this earlier this year with the same device - amongst another pool after scrubbing didn't resumed as expected. The import of the pool above in question works by using the very first id: id: 257822624560506537. But what is with the other IDs? What are those IDs and labels doing here? Is it possible that ZFS has some bugs revealing older labels/GUIDs of the device from a earlier configuration than the last one configured and prepared for?=20 How can I get rid of those fake/phantom id? Rgards, Oliver --Sig_/z9kSIl0Em4M+oyfKrrubaOh Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBAgAGBQJR73KbAAoJEOgBcD7A/5N8LXgH/RplRyulEAtQxoKDXNvjRABY I1T1pmFCmZ2EzPIzTJfnHdOltcq+laAWSa442IMtmUPrww1I2aK8DxpXQPCQRQ/3 b0wUFkyeFYV2vpbhWUO/vkfnlpi9a1atSGBkrGvJVvxYykJodWCmHXzwYTqmhgZM arxjTiBAby9Xv0Hkik3LJShNyo0N9AblOKa9J3aq1bRHsnqO34BKxKJxV9nYKp+G p/QA1W0kbP8OciZx7luyqQAr1lPeU9jHJpB5vlK8Axhb8gr9HC8zCsmUyqnveJQc uD6eHqCKCsuPAIipe84IXc2PIpLOIFwuxxgfgyOUQWm5mNujcYp+y4IFKYeE640= =PWOa -----END PGP SIGNATURE----- --Sig_/z9kSIl0Em4M+oyfKrrubaOh--