Date: Fri, 22 Sep 2006 08:39:00 -0500 From: "Rick C. Petty" <rick-freebsd@kiwi-computer.com> To: freebsd-geom@FreeBSD.ORG Subject: Re: geom - help ... Message-ID: <20060922133900.GA31626@megan.kiwi-computer.com> In-Reply-To: <200609220914.k8M9E1h8077566@lurza.secnetix.de> References: <20060921200909.GA13927@megan.kiwi-computer.com> <200609220914.k8M9E1h8077566@lurza.secnetix.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 22, 2006 at 11:14:01AM +0200, Oliver Fromme wrote: > Rick C. Petty wrote: > > Is everybody forgetting about gvinum? > > I _try_ to forget it. :-) Exactly the type of attitude I predicted. So let's force everybody who has terabytes in vinum-managed containers to migrate! I mean, who *doesn't* have a few extra TB of disk space available to aid with that migration? > Seriously, we've been running vinum with FreeBSD 4.x for > six years. When upgrading to 6.x (skipping 5.x entirely), > we changed to gmirror, and my impression is that it is > much better and easier to manage. I really like it. Once I wouldn't say it's at all better, although it was easier to setup just a mirror. Vinum is a volume manager, so I expect it to be more complex than just setting up a mirror. But I certainly wouldn't call it better. My mirror rebuilds *every* power outtage (and sometimes even at expected shutdowns), a behavior I have not witnessed with gvinum. I have yet to see anyone address the inability to change your geom containers when dealing with live filesystems. Until this is "fixed", comparing gvinum to other geom classes is apples to oranges. If you haven't yet been bitten by this problem, then it's no wonder you really like it. > you're familiar with the GEOM concepts, vinum seems to be > an unnecessarily complex and inflexible beast. > > That's just my personal opinion, of course, YMMV. I am quite familiar with GEOM and I was sad the day vinum was dropped and gvinum wasn't even close to par with it. It has since improved. I wouldn't say it's unnecessarily complex or at all inflexible, maybe you're just not used to managing lots of large volumes? I agree that geom is more flexible, and once all the bugs are worked out of all the layers, maybe someone will write "fvm" to make managing the volumes easier. I like g/vinum's ability to edit the entire infrastructure from a single configuration file. Having to repeatedly type a hundred geom commands sounds like room for human error. Your opinion noted and ignored. I'm glad others agree with g/vinum's importance, or all the poor admins with vinum-managed volumes would be left out in the cold. -- Rick C. Petty
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060922133900.GA31626>