From owner-freebsd-current@FreeBSD.ORG Wed May 15 17:20:56 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 6E08436B for ; Wed, 15 May 2013 17:20:56 +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]) by mx1.freebsd.org (Postfix) with ESMTP id 2D7A0E45 for ; Wed, 15 May 2013 17:20:55 +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 <1UcfNg-000fpw-OP>; Wed, 15 May 2013 19:20:48 +0200 Received: from g229089158.adsl.alicedsl.de ([92.229.89.158] helo=[192.168.0.128]) by inpost2.zedat.fu-berlin.de (Exim 4.80.1) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1UcfNg-002ZnK-Jg>; Wed, 15 May 2013 19:20:48 +0200 Subject: CURRENT r250636: ZFS pool destroyed while scrubbing in action and shutdown From: "O. Hartmann" To: FreeBSD Current Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-m5gvLniz0t/9nhcONi8L" Date: Wed, 15 May 2013 19:20:48 +0200 Message-ID: <1368638448.1549.5.camel@thor.walstatt.dyndns.org> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-Originating-IP: 92.229.89.158 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, 15 May 2013 17:20:56 -0000 --=-m5gvLniz0t/9nhcONi8L Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Several machines running=20 FreeBSD 10.0-CURRENT #0 r250636: Tue May 14 21:13:19 CEST 2013 amd64 were scrubbing the pools over the past two days. Since that takes a while, I was sure I could shutdown the boxes and scrubbing will restart next restart automatically. Not this time! On ALL(!) systems (three) the pools remains destroyed/corrupted showing this message(s) (as a representative, I will present only one): zpool status pool: ASGARD00 state: FAULTED status: The pool metadata is corrupted and the pool cannot be opened. action: Recovery is possible, but will result in some data loss. Returning the pool to its state as of Wed May 15 08:36:02 2013 should correct the problem. Approximately 7 seconds of data must be discarded, irreversibly. After rewind, several persistent user-data errors will remain. Recovery can be attempted by executing 'zpool clear -F ASGARD00'. A scrub of the pool is strongly recommended after recovery. see: http://illumos.org/msg/ZFS-8000-72 scan: none requested config: NAME STATE READ WRITE CKSUM ASGARD00 FAULTED 0 0 1 raidz1-0 ONLINE 0 0 8 gptid/1e716118-1492-11e2-b828-90f6526a24d6 ONLINE 0 0 0 gptid/294a6798-1492-11e2-b828-90f6526a24d6 ONLINE 0 0 0 gptid/30c813f8-1492-11e2-b828-90f6526a24d6 ONLINE 0 0 1 logs ada0p1 ONLINE 0 0 0 This happened on all systems. Another ZFS pool has only one disk, it also happened to fail and being corrupt. --=-m5gvLniz0t/9nhcONi8L Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (FreeBSD) iQEcBAABAgAGBQJRk8PrAAoJEOgBcD7A/5N844wH/jacFDfQhYSUwHaNLEpKPVSU jOGcc0xY3caHeEzukndeDn3+4RmG/vKXYLfjR3RS0VA6S/OY0+Ae8KjyKY0j/KKj B73yF5iRsQYMhLXOIM3tjMKDZ2uIxJGFckuaWKCTMlaznXRRlxZu83vpKYlIchqA dNAXTP9RpOx/3snsns9LWWNnSRMXHOvq0w1fLHXXELxAjlUyIzqI/5fV5B0xLDP8 FbxhNhpmXoUvYyBliE3d0hD4S8cZaudvo7drl472dGdmExheP2m1WzkLqj24YSBU bPx6Iw/GPd0ZP4F21JrcvcSaffwDs+VW41jbI9Uyt9lsw2qnPRw3IuSrq6ApuGQ= =Xqoj -----END PGP SIGNATURE----- --=-m5gvLniz0t/9nhcONi8L--