Date: Fri, 6 Aug 2004 08:38:06 -0500 From: Craig Boston <craig@xfoil.gank.org> To: Paul Mather <paul@gromit.dlib.vt.edu> Cc: Lukas Ertl <le@FreeBSD.org> Subject: Re: Vinum status Message-ID: <20040806133806.GA30900@nowhere> In-Reply-To: <1091761575.860.22.camel@zappa.Chelsea-Ct.Org> References: <20040726191107.B10DD16A513@hub.freebsd.org> <1091130224.99074.55.camel@zappa.Chelsea-Ct.Org> <20040729215647.F625@korben.in.tern> <1091460946.46029.22.camel@zappa.Chelsea-Ct.Org> <20040805212025.GA28645@nowhere> <1091761575.860.22.camel@zappa.Chelsea-Ct.Org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 05, 2004 at 11:06:16PM -0400, Paul Mather wrote: > The only time I've had a problem is when I last built a kernel (today, > actually) and forgot to build geom_vinum.ko manually. Needless to say, > the next boot failed to find my root partition due to the missing kernel > module. Luckily, rebooting using /boot/kernel.old allowed me to build > and install geom_vinum.ko and boot my new kernel successfully. It would be nice if geom_vinum and gvinum could be hooked up to the build. There are quite a few people using them now and they seem to be "usable enough" (for CURRENT anyway). I don't think it would hurt anything as the user would still have to configure it manually -- it's not going to start stealing drives away from non-GEOM vinum I don't think. > I mentioned on freebsd-current that round-robin reads don't seem to be > supported by geom_vinum, yet. (Lukas confirmed this is yet to be > done.) In my system, all reads are from one drive of my mirror, unlike > with the old vinum. Perhaps this is partially the cause of the relative > slowness you're seeing? I wonder how this is handled in the RAID5 case, where you don't really have a choice. You either have to round robin read, or read all the drives and suffer the parity calculation penalty. /off to check the source... > It'd be great to see GEOM vinum go into 5.3, and hence be adopted for > 5-STABLE. Great work, Lukas! Agreed, I'm quite happy that I can swap over vinum again without md(4) hacks. Straight GEOM classes may eventually be more flexible, but for now vinum is still the simplest way to get volume management. Having a clean upgrade path from 4.x is a very good thing too. -- Craig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040806133806.GA30900>