Date: Thu, 29 Jul 2004 15:43:45 -0400 From: Paul Mather <paul@gromit.dlib.vt.edu> To: freebsd-current@freebsd.org Subject: Re: Vinum status Message-ID: <1091130224.99074.55.camel@zappa.Chelsea-Ct.Org> In-Reply-To: <20040726191107.B10DD16A513@hub.freebsd.org> References: <20040726191107.B10DD16A513@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 26 Jul 2004 14:30:04 +0200 (CEST), Lukas Ertl <le@FreeBSD.org>
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1091130224.99074.55.camel>