From owner-freebsd-current@FreeBSD.ORG Thu Jul 29 19:44:11 2004 Return-Path: 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 00EA716A4CE; Thu, 29 Jul 2004 19:44:11 +0000 (GMT) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.49.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id A861743D48; Thu, 29 Jul 2004 19:44:10 +0000 (GMT) (envelope-from paul@gromit.dlib.vt.edu) Received: from hawkwind.Chelsea-Ct.Org (pool-151-199-91-61.roa.east.verizon.net [151.199.91.61]) by gromit.dlib.vt.edu (8.12.11/8.12.11) with ESMTP id i6TJhqdx023875 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 29 Jul 2004 15:43:53 -0400 (EDT) (envelope-from paul@gromit.dlib.vt.edu) Received: from [192.168.1.25] (zappa [192.168.1.25])i6TJhkJX015819; Thu, 29 Jul 2004 15:43:46 -0400 (EDT) From: Paul Mather To: freebsd-current@freebsd.org In-Reply-To: <20040726191107.B10DD16A513@hub.freebsd.org> References: <20040726191107.B10DD16A513@hub.freebsd.org> Content-Type: text/plain Message-Id: <1091130224.99074.55.camel@zappa.Chelsea-Ct.Org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 29 Jul 2004 15:43:45 -0400 Content-Transfer-Encoding: 7bit Subject: Re: Vinum status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 29 Jul 2004 19:44:11 -0000 On Mon, 26 Jul 2004 14:30:04 +0200 (CEST), Lukas Ertl wrote: > On Sun, 25 Jul 2004, Matthias Schuendehuette wrote: [[...]] > > Another problem occurs if geom_vinum.ko is loaded via loader.conf - it > > does not panic any more (as it does about two weeks ago), but it does > > not collect all subdisks of a RAID5-plex *at boottime*. If I start > > gvinum if the system is up (multiuser), there are no problems any more > > collecting *all* subdisks available... > > That should be fixed by now. Does this imply that root-on-gvinum is working now? Last time I tried it (shortly after gvinum was committed to the tree), it worked except that only half of the drives, plexes, and volumes in my Vinum RAID 1 mirror were detected when the gvinum module read the configuration from the drives during boot. I think root-on-gvinum not working is the only definite show-stopper I can see for Vinum support when upgrading to 5.3, as far as I'm concerned. Lack of root-on-gvinum would prevent me from upgrading my 5.2.1-RELEASE-p9 system to 5.3-RELEASE. :-( I have two identical spare drives for my -CURRENT system I can (ab)use for testing... Cheers, Paul. -- e-mail: paul@gromit.dlib.vt.edu "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." --- Frank Vincent Zappa