From owner-freebsd-current@FreeBSD.ORG  Sat Oct 15 11:32:13 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@FreeBSD.org
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 642C016A41F;
	Sat, 15 Oct 2005 11:32:13 +0000 (GMT)
	(envelope-from daniel_k_eriksson@telia.com)
Received: from pne-smtpout2-sn2.hy.skanova.net
	(pne-smtpout2-sn2.hy.skanova.net [81.228.8.164])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C7AC343D48;
	Sat, 15 Oct 2005 11:32:12 +0000 (GMT)
	(envelope-from daniel_k_eriksson@telia.com)
Received: from royal64.emp.zapto.org (195.198.193.104) by
	pne-smtpout2-sn2.hy.skanova.net (7.2.060.1)
	id 434E604000058AFD; Sat, 15 Oct 2005 13:32:11 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 15 Oct 2005 13:32:11 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Message-ID: <4F9C9299A10AE74E89EA580D14AA10A605F566@royal64.emp.zapto.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: gvinum startup problems
Thread-Index: AcXNaHZDxrOwrmkoTMu3yXPVvKfWmAEEsRgg
From: "Daniel Eriksson" <daniel_k_eriksson@telia.com>
To: <freebsd-current@FreeBSD.org>
Cc: Lukas Ertl <le@FreeBSD.org>
Subject: RE: gvinum startup problems
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Oct 2005 11:32:13 -0000


It looks like the gvinum problems I've been having were due to some sort
of metadata inconsistency. After manually setting the stale subdisks to
the "up" state and then doing a 'gvinum saveconfig', gvinum now is able
to pick up the array during boot just fine.

What threw me off was the fact that manually loading gvinum worked fine,
so when auto-loading gvinum resulted in a broken array I never
considered metadata problems.

/Daniel Eriksson