From owner-freebsd-current@FreeBSD.ORG Wed Dec 6 10:41:47 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5ADB216A412 for ; Wed, 6 Dec 2006 10:41:47 +0000 (UTC) (envelope-from lulf@stud.ntnu.no) Received: from merke.itea.ntnu.no (merke.itea.ntnu.no [129.241.7.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC82044A4E for ; Wed, 6 Dec 2006 10:21:11 +0000 (GMT) (envelope-from lulf@stud.ntnu.no) Received: from localhost (localhost [127.0.0.1]) by merke.itea.ntnu.no (Postfix) with ESMTP id 599EE13C79F; Wed, 6 Dec 2006 11:21:52 +0100 (CET) Received: from gaupe.stud.ntnu.no (gaupe.stud.ntnu.no [129.241.56.184]) by merke.itea.ntnu.no (Postfix) with ESMTP; Wed, 6 Dec 2006 11:21:46 +0100 (CET) Received: by gaupe.stud.ntnu.no (Postfix, from userid 2312) id CC9A5D0018; Wed, 6 Dec 2006 11:23:03 +0100 (CET) Date: Wed, 6 Dec 2006 11:23:03 +0100 From: Ulf Lilleengen To: Eric Germann Message-ID: <20061206102300.GA17808@stud.ntnu.no> References: <0dbf01c71782$a57cdf00$79001cac@EKGLAPTOPCC> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0dbf01c71782$a57cdf00$79001cac@EKGLAPTOPCC> User-Agent: Mutt/1.5.9i X-Content-Scanned: with sophos and spamassassin at mailgw.ntnu.no. Cc: freebsd-current@freebsd.org Subject: Re: Updating a server with Vinum X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 10:41:47 -0000 On man, des 04, 2006 at 04:00:28 -0500, Eric Germann wrote: > I've got an old server I'm looking to slap -CURRENT on. It has a RAID5 > Vinum array and is running 4.3R (yes I know, really old ...) > > My question is this: If I bring it up into the 6.x train of either -STABLE > or -CURRENT, will the new vinum drivers recognize the old config written to > the drives? Of course backup is important, but just curious how it would > handle this. It would be nice not to have to recreate it and restore it. > Gvinum uses the same parts and the same format on the configuration as vinum and should be fully backwards-compatible. If not, that is a bug in gvinum. A difference will be that the volumes are in /dev/gvinum and not in /dev/vinum as before. Other than that, gvinum in RELENG_6 is decent from my experience. As you said, just take backup :) -- Ulf Lilleengen