From owner-freebsd-questions@FreeBSD.ORG  Fri Aug 19 16:01:57 2005
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
X-Original-To: freebsd-questions@freebsd.org
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 16CA716A41F
	for <freebsd-questions@freebsd.org>;
	Fri, 19 Aug 2005 16:01:57 +0000 (GMT)
	(envelope-from rasmith@aristotle.tamu.edu)
Received: from aristotle.tamu.edu (Aristotle.tamu.edu [165.91.161.90])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B283443D49
	for <freebsd-questions@freebsd.org>;
	Fri, 19 Aug 2005 16:01:56 +0000 (GMT)
	(envelope-from rasmith@aristotle.tamu.edu)
Received: from aristotle.tamu.edu (localhost [127.0.0.1])
	by aristotle.tamu.edu (8.13.1/8.13.1) with ESMTP id j7JG1uTf090350
	for <freebsd-questions@freebsd.org>;
	Fri, 19 Aug 2005 11:01:56 -0500 (CDT)
	(envelope-from rasmith@aristotle.tamu.edu)
Message-Id: <200508191601.j7JG1uTf090350@aristotle.tamu.edu>
To: freebsd-questions@freebsd.org
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Date: Fri, 19 Aug 2005 11:01:55 -0500
From: Robin Smith <rasmith@aristotle.tamu.edu>
Subject: Vinum migration 4.x-5.4
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2005 16:01:57 -0000

There seems to be a consensus in the references I've found that vinum
is completely broken on 5.4 and that gvinum/geom_vinum is not ready
for production use.  As it seems to me, this means that anyone using
4.11 (say) and vinum will have to abandon vinum (i.e. quit doing software
RAID) in order to upgrade to 5.4.  That can be both laborious and slow
(e.g. if you have /usr on, say, a four-drive vinum volume in 4.11, you're
going to have to replace those drives with something else in order to go
to 5.4.  Is that false, and is there a relatively simple way to get 
geom_vinum in 5.4 to read a vinum configuration produced under 4.11 and
start the vinum volume as it is?

Robin Smith