Date: Fri, 19 Aug 2005 20:09:07 +0200 From: Stijn Hoop <stijn@win.tue.nl> To: Robin Smith <rasmith@aristotle.tamu.edu> Cc: freebsd-questions@freebsd.org Subject: Re: Vinum migration 4.x-5.4 Message-ID: <20050819180907.GV61271@pcwin002.win.tue.nl> In-Reply-To: <200508191601.j7JG1uTf090350@aristotle.tamu.edu> References: <200508191601.j7JG1uTf090350@aristotle.tamu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--y9PDtDHaFrXNoMPU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Aug 19, 2005 at 11:01:55AM -0500, Robin Smith wrote:
> There seems to be a consensus in the references I've found that vinum
> is completely broken on 5.4
That is true. IMHO it should be removed from RELENG_5 and _6 if it isn't
already.
> and that gvinum/geom_vinum is not ready for production use.
Well the only reason it might not be is that it hasn't seen widespread
testing, as far as I can tell it should all just work. I do use gvinum
on a 5-STABLE host and it has worked well for me in the past [1].
> As it seems to me, this means that anyone using
> 4.11 (say) and vinum will have to abandon vinum (i.e. quit doing software
> RAID) in order to upgrade to 5.4.
5.4 does have alternatives to vinum (which is another reason why gvinum
hasn't received as much testing): gmirror, graid3, gstripe, gconcat.
> That can be both laborious and slow
> (e.g. if you have /usr on, say, a four-drive vinum volume in 4.11, you're
> going to have to replace those drives with something else in order to go
> to 5.4.
I'd say building a new test box is about the only sane way to do it.
> Is that false, and is there a relatively simple way to get=20
> geom_vinum in 5.4 to read a vinum configuration produced under 4.11 and
> start the vinum volume as it is?
As far as I can tell, it should just work. To pick up the latest round
of vinum fixes it might be best to run 5-STABLE (ie. RELENG_5) but it
should not be necessary unless you run into difficulties.
But the only way to know for sure if things work, is to test...
--Stijn
[1] for some reason I discovered a configuration problem earlier this
week, but the other part of the mirror is holding up and it seems
that I can reconstruct the broken part this weekend. If anything,
it seems that a gvinum mirrored plex is robust.
--=20
"Coca-Cola is solely responsible for ensuring that people - too stupid to k=
now
not to tip half-ton machines on themselves - are safe. Forget parenting - t=
he
blame is entirely on the corporation for designing machines that look so
innocent and yet are so deadly."
-- http://www.kuro5hin.org/?op=3Ddisplaystory;sid=3D2001/10/28/212418/42
--y9PDtDHaFrXNoMPU
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)
iD8DBQFDBiBDY3r/tLQmfWcRAq1sAJsEkEfaxlVq25kviyj6sXkLWUMlXACggQtt
raEPjh8y20yWEN9L8vqH8lY=
=yaIm
-----END PGP SIGNATURE-----
--y9PDtDHaFrXNoMPU--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050819180907.GV61271>