Date: Fri, 15 Jul 2005 10:04:31 -0400 From: Ean Kingston <ean@hedron.org> To: freebsd-questions@freebsd.org Subject: Re: FreeBSD 5.x raid... Message-ID: <200507151004.32085.ean@hedron.org> In-Reply-To: <6F47B75F-86F4-41FF-B9D5-31E9BDC2C4D7@HiWAAY.net> References: <42D6683E.7040406@os.lv> <42D709AC.4080002@os.lv> <6F47B75F-86F4-41FF-B9D5-31E9BDC2C4D7@HiWAAY.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On July 14, 2005 11:42 pm, David Kelly wrote: > On Jul 14, 2005, at 7:56 PM, Casper wrote: > > I can`t find gvinum man on my 5.4 and in google too :) Use the vinum manpage and documentation just mentally substitute gvinum for vinum in all commands. Also, as mentioned before, gvinum is not yet feature complete so some of the things listed in the documentation for vinum doesn't work yet. It's sort of hit-and-miss. There is enough of gvinum to be able to setup a mirror (I did that on 5.3). Also, if upgrading from a 4.x system gvinum will read the vinum config from the disk BUT after you run gvinum the first time you may have problems getting back to vinum (according to the readme). The change in name from vinum to gvinum is because of the new disk sub-system (geom). IIRC It is optional in late version of 4.x and early versions of 5.x. It's off by default in 4.x and on by default in 5.x. > What I was told a year ago was that vinum development and support in > the 5.x series had ceased and that gvinum was slated to replace > vinum. As I said previously vinum worked once running but had about a > 50/50 probability of remembering my configuration between reboots. > Simply changing the startup file /etc/rc.d/vinum to start gvinum > rather than vinum solved the problem completely using the drives > configured with vinum without rebuilding the volume. > > Gvinum is necessary due to internal changes in FreeBSD due to GEOM. > > It has also been said that gvinum does not yet have all the features > of vinum. What its lacking, I can't say. > > > I`m thinking for my server better tool is gmirror? > > Gvinum worked for my striped volume. I can't say how gmirror differs > from gvinum. Maybe someone who has run both will speak. > > The "gvinum mirror" command I provided earlier should have you up and > running very quickly. Suggest you try it. Beat on the system. > Practice removing a plex, trashing it as if it were a new drive, then > rebuilding the mirror. Then do the same for gmirror. Now is the right > time to play with it before the system goes into production and > becomes too precious to play with. > > -- > David Kelly N4HHE, dkelly@HiWAAY.net > ======================================================================== > Whom computers would destroy, they must first drive mad. > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" -- Ean Kingston E-Mail: ean AT hedron DOT org URL: http://www.hedron.org/ I am currently looking for work. If you need competent system/network administration please feel free to contact me directly.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200507151004.32085.ean>