From owner-freebsd-geom@FreeBSD.ORG  Thu Aug  4 08:53:48 2005
Return-Path: <owner-freebsd-geom@FreeBSD.ORG>
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 7C37716A41F;
	Thu,  4 Aug 2005 08:53:48 +0000 (GMT)
	(envelope-from snow@teardrop.org)
Received: from imladris.teardrop.org (imladris.teardrop.org [66.92.66.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2F4C143D49;
	Thu,  4 Aug 2005 08:53:48 +0000 (GMT)
	(envelope-from snow@teardrop.org)
Received: by imladris.teardrop.org (Postfix, from userid 100)
	id 98F04BE20F; Thu,  4 Aug 2005 04:53:57 -0400 (EDT)
Date: Thu, 4 Aug 2005 04:53:57 -0400
From: James Snow <snow@teardrop.org>
To: Pawel Jakub Dawidek <pjd@FreeBSD.org>
Message-ID: <20050804085357.GA18756@teardrop.org>
References: <20050803012515.GA1227@teardrop.org>
	<20050803055847.GD59370@garage.freebsd.pl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050803055847.GD59370@garage.freebsd.pl>
User-Agent: Mutt/1.4.2.1i
Cc: freebsd-geom@freebsd.org
Subject: Re: gmirror on boot device after upgrade from 5.4 to 6.0?
X-BeenThere: freebsd-geom@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: GEOM-specific discussions and implementations
	<freebsd-geom.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-geom>,
	<mailto:freebsd-geom-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-geom>
List-Post: <mailto:freebsd-geom@freebsd.org>
List-Help: <mailto:freebsd-geom-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-geom>,
	<mailto:freebsd-geom-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2005 08:53:48 -0000

On Wed, Aug 03, 2005 at 07:58:47AM +0200, Pawel Jakub Dawidek wrote:
>
> Please, provide more details asap, so I can work on issues before 6.0.

Pawel,

Once I rebuilt from whatever 6-CURRENT I was running to 6.0-BETA2 my
troubles appeared to go away. I guess I was bumping into an old and
already fixed bug. Sorry for the false alarm.

By the way, gmirror behaved quite nicely through this. I was able to
boot from one of the providers with gmirror disabled, load gmirror,
deactivate the other provider, build an up-to-date kernel and install
it, and then reboot onto the gmirror device, reactivate the second
provider and have it start syncing back up. Thanks for your work on
gmirror.


-Snow