From owner-freebsd-geom@FreeBSD.ORG Tue Oct 31 21:00:51 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 4590316A558 for ; Tue, 31 Oct 2006 21:00:51 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9990243D53 for ; Tue, 31 Oct 2006 21:00:50 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id k9VL0ms7036825; Tue, 31 Oct 2006 15:00:48 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <4547B983.4020802@centtech.com> Date: Tue, 31 Oct 2006 15:00:51 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.7 (X11/20061015) MIME-Version: 1.0 To: rick-freebsd@kiwi-computer.com References: <20061031195442.GA55478@keira.kiwi-computer.com> <4547AD9B.5050503@centtech.com> <20061031204659.GA56766@keira.kiwi-computer.com> In-Reply-To: <20061031204659.GA56766@keira.kiwi-computer.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2134/Tue Oct 31 14:10:21 2006 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com 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 21:00:51 -0000 On 10/31/06 14:46, Rick C. Petty wrote: > On Tue, Oct 31, 2006 at 02:10:03PM -0600, Eric Anderson wrote: > >> You probably need to do a gmirror forget, then a gmirror remove (on >> ad8), then re-insert it. > > The forget seemed to fix it. FYI: > > # gmirror remove gm0 ad8 > No such provider: ad8. > > I'm not sure if that step was even necessary. At least now both ad4 and > ad8 are listed and are of the same size. I was worried gmirror would try > to allocate its metadata on ad8 twice. I don't know why I thought that, > because gmirror would treat the ad8 as a provider and overwrite any > previous metadata when doing a "gmirror insert". > >> gmirror probably kicked it out because of errors? > > I guess that's what my question was really trying to get at. What caused > the error, what was the error, and why did gmirror both not recognize ad8 > and also think there was a missing disk. I guess if it was expecting a > specific ID and ad8 no longer had that ID (it got wiped for some odd > reason?) it would behave as such. That explains the last question. The > first two are hard to diagnose w/o dmesg. :( If the disk has enough trouble, gmirror will kick it out of the mirror and mark it as such. It won't re-add the disk to the mirror (it still thinks it's a bad drive) unless you manually force it to (which you did with the forget). It wouldn't let you insert it, because it was already known to the mirror. > 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 gmirror > configurations in case the metadata gets clobbered. I don't think it did get clobbered. I think things went exactly as it should have actually. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------