From owner-freebsd-geom@FreeBSD.ORG Tue Oct 31 20:59:20 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F36E216A492 for ; Tue, 31 Oct 2006 20:59:19 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 450A443D53 for ; Tue, 31 Oct 2006 20:59:12 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 5D43A45685; Tue, 31 Oct 2006 21:59:10 +0100 (CET) Received: from localhost (dkm191.neoplus.adsl.tpnet.pl [83.24.16.191]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 5DBBF45681; Tue, 31 Oct 2006 21:58:57 +0100 (CET) Date: Tue, 31 Oct 2006 21:58:57 +0100 From: Pawel Jakub Dawidek To: "Rick C. Petty" Message-ID: <20061031205857.GA15861@garage.freebsd.pl> References: <20061031195442.GA55478@keira.kiwi-computer.com> <4547AD9B.5050503@centtech.com> <20061031204659.GA56766@keira.kiwi-computer.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zhXaljGHf11kAtnf" Content-Disposition: inline In-Reply-To: <20061031204659.GA56766@keira.kiwi-computer.com> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-geom@freebsd.org Subject: Re: burnt again by gmirror X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Oct 2006 20:59:20 -0000 --zhXaljGHf11kAtnf Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 31, 2006 at 02:46:59PM -0600, Rick C. Petty wrote: > On Tue, Oct 31, 2006 at 02:10:03PM -0600, Eric Anderson wrote: >=20 > > You probably need to do a gmirror forget, then a gmirror remove (on > > ad8), then re-insert it. >=20 > The forget seemed to fix it. FYI: >=20 > # gmirror remove gm0 ad8 > No such provider: ad8. >=20 > I'm not sure if that step was even necessary. At least now both ad4 and = =20 > ad8 are listed and are of the same size. I was worried gmirror would try= =20 > to allocate its metadata on ad8 twice. I don't know why I thought that, = =20 > because gmirror would treat the ad8 as a provider and overwrite any=20 > previous metadata when doing a "gmirror insert". >=20 > > gmirror probably kicked it out because of errors? >=20 > I guess that's what my question was really trying to get at. What caused= =20 > the error, what was the error, and why did gmirror both not recognize ad8= =20 > and also think there was a missing disk. I guess if it was expecting a = =20 > specific ID and ad8 no longer had that ID (it got wiped for some odd=20 > reason?) it would behave as such. That explains the last question. The = =20 > first two are hard to diagnose w/o dmesg. :( >=20 > Still, I'm curious why/how ad8's metadata could have been clobbered. > gmirror is the only one who would write to it, the filesystem is mounted > from gm0* -- kinda scary. I guess the lesson here is to use simple gmirr= or > configurations in case the metadata gets clobbered. gmirror told you that it think ad8 is broken and skipped it. If an error is discovered on mirror's component it is marked as broken and disconnected so it doesn't case further problems. For example disk problem is that it doesn't complete I/O requests and gmirror need to wait for ATA timeouts, which will make the whole system unresponsive. If component was disconnected it means something was wrong with it and it needs manual intervention and investigation. I'm sure your logs would tell you. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --zhXaljGHf11kAtnf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFFR7kRForvXbEpPzQRAusvAJ9v6CsmkSIyRgQ32qhZuzUK7gnfswCgwkQA pm0ib8oCrjw9rQAkBJ/Frto= =EGuW -----END PGP SIGNATURE----- --zhXaljGHf11kAtnf--