From owner-freebsd-geom@FreeBSD.ORG Mon Nov 8 13:06:19 2004 Return-Path: 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 71D6C16A4E2; Mon, 8 Nov 2004 13:06:19 +0000 (GMT) Received: from thekla.de.clara.net (thekla.de.clara.net [212.82.225.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA65643D4C; Mon, 8 Nov 2004 13:06:18 +0000 (GMT) (envelope-from michael.riexinger@de.clara.net) Received: from localhost.de.clara.net ([127.0.0.1] helo=localhost) by thekla.de.clara.net with esmtp (Exim 4.30; FreeBSD) id 1CR9Dt-000DJ7-VT; Mon, 08 Nov 2004 14:06:18 +0100 Received: from box.int.de.clara.net ([192.168.0.226]) by thekla.de.clara.net with esmtp (Exim 4.30; FreeBSD) id 1CR9Dt-000DJ3-Qa; Mon, 08 Nov 2004 14:06:17 +0100 From: Michael Riexinger To: Pawel Jakub Dawidek Date: Mon, 8 Nov 2004 14:06:49 +0100 User-Agent: KMail/1.7 References: <200411081140.57792.michael.riexinger@de.clara.net> <200411081247.39449.michael.riexinger@de.clara.net> <20041108115506.GB8120@darkness.comp.waw.pl> In-Reply-To: <20041108115506.GB8120@darkness.comp.waw.pl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411081406.50208.michael.riexinger@de.clara.net> cc: freebsd-geom@freebsd.org Subject: Re: gmirror problems X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 13:06:19 -0000 On Monday 08 November 2004 12:55, Pawel Jakub Dawidek wrote: > On Mon, Nov 08, 2004 at 12:47:38PM +0100, Michael Riexinger wrote: > +> On Monday 08 November 2004 12:05, Pawel Jakub Dawidek wrote: > +> > On Mon, Nov 08, 2004 at 11:40:57AM +0100, Michael Riexinger > wrote: +> > +> Hi, > +> > +> > +> > +> I set up FreeBSD 5.3 with gmirror for my 2 ide disks ad0 and > ad1. +> > So the +> rootfs is included in the mirror. I wanted to > test what +> > happens when +> one disk fails, so I removed ad1. > Unfortunately after +> > a reboot the +> system didn't boot anymore > with the error: +> > +> GEOM_MIRROR: Force device mirror0 start due > to timeout +> > +> and > +> > +> GEOM_MIRROR: Device mirror0 destroyed > +> > > +> > Could you add: > +> > > +> > kern.geom.mirror.debug=2 > +> > > +> > to your /boot/loader.conf and try to boot without ad1 again. > +> > It should start mirror with only one component (ad0) connected > after +> > this timeout and now it looks like it can't find any > component. +> Ok, done that: > +> > +> the messages are: > +> GEOM_MIRROR[2]: Tasting ad0. > +> magic: GEOM::MIRROR > +> version: 1 > +> name: mirror0 > +> did: 1626481947 > +> all: 2 > +> syncid: 1 > +> priority: 0 > +> slice: 4096 > +> balance: load > +> mediasize: 20485785088 > +> vectorsize: 512 > +> syncoffset: 1297612800 > +> mflags: NONE > +> dflags: DIRTY SYNCHONIZING > > Ok, everything is clear now. You disconnected ad1, but ad0 was marked > for synchronization. It that case gmirror cannot find any valid > component, because the only one it can find is stale. > So: > 1. You should test it when mirror is in complete state (then you can > remove any component). Ok, thanks, done that. Now both ad0 and ad1 are in dirty state. What exactly means dirty? I found nothing about it in the manpage. Kind regards, Michael Riexinger systems engineer -- claranet gmbh internet service provider tel +49 (0) 69 - 40 80 18 - 300 email: michael.riexinger@de.clara.net http://www.claranet.de/