From owner-freebsd-geom@FreeBSD.ORG  Sun Aug 12 02:10:54 2007
Return-Path: <owner-freebsd-geom@FreeBSD.ORG>
Delivered-To: freebsd-geom@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id BB66316A417
	for <freebsd-geom@freebsd.org>; Sun, 12 Aug 2007 02:10:54 +0000 (UTC)
	(envelope-from hg@queue.to)
Received: from pickle.queue.to (pickle.queue.to [71.180.69.18])
	by mx1.freebsd.org (Postfix) with ESMTP id 3E47413C442
	for <freebsd-geom@freebsd.org>; Sun, 12 Aug 2007 02:10:54 +0000 (UTC)
	(envelope-from hg@queue.to)
Received: (qmail 83316 invoked from network); 11 Aug 2007 21:44:12 -0400
Received: from cally.queue.to (172.16.0.6)
	by pickle.queue.to with ESMTP; 11 Aug 2007 21:44:12 -0400
Message-ID: <46BE65EC.1050906@queue.to>
Date: Sat, 11 Aug 2007 21:44:12 -0400
From: Howard Goldstein <hg@queue.to>
User-Agent: Thunderbird 2.0.0.6 (X11/20070802)
MIME-Version: 1.0
To: freebsd-geom@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: graid5 or gvinums - bootable?
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: Sun, 12 Aug 2007 02:10:54 -0000

Apologies in advance for the dumb question.  I request a reality check
here as it takes a few hours (on graid5 at least) on my hardware for the
provider to sync and this is on a production box I can't take down for
too long.

Q: Should a graid5 or gvinum provider be expected to be bootable,
assuming the prover's partition table has an active bootable partition
containing a properly bsdlabeled 'a' slice with the /boot subdirectories
in it (i.e., all of the stuff you normally need in an ordinary, non-geom
 system to have a bootable slice)?

Teh googling is somewhat helpful indicating that the boot loader can now
deal with the GEOM'd gvinum as the boot device, and of course it works
with gmirror but that's not really surprising since that provider
wouldn't doesn't have its /boot slice striped into ribbons across
multiple consumers like graid5 and gvinum in raid-5.