From owner-freebsd-questions@FreeBSD.ORG Thu Nov 11 15:09:51 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4320B16A4CE for ; Thu, 11 Nov 2004 15:09:51 +0000 (GMT) Received: from kweetal.tue.nl (kweetal.tue.nl [131.155.3.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 974B743D1D for ; Thu, 11 Nov 2004 15:09:50 +0000 (GMT) (envelope-from stijn@pcwin002.win.tue.nl) Received: by kweetal.tue.nl (Postfix, from userid 40) id C889713B721; Thu, 11 Nov 2004 16:09:49 +0100 (CET) Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by kweetal.tue.nl (Postfix) with ESMTP id 70AC213B719; Thu, 11 Nov 2004 16:09:48 +0100 (CET) Received: (from stijn@localhost) by pcwin002.win.tue.nl (8.13.1/8.13.1/Submit) id iABF9mhO004818; Thu, 11 Nov 2004 16:09:48 +0100 (CET) (envelope-from stijn) Date: Thu, 11 Nov 2004 16:09:48 +0100 From: Stijn Hoop To: Kim Helenius Message-ID: <20041111150948.GE635@pcwin002.win.tue.nl> Mail-Followup-To: Stijn Hoop , Kim Helenius , freebsd-questions@freebsd.org References: <20041111121746.GY912@pcwin002.win.tue.nl> <20041111133935.GC635@pcwin002.win.tue.nl> <41937CF3.70502@cc.jyu.fi> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IMjqdzrDRly81ofr" Content-Disposition: inline In-Reply-To: <41937CF3.70502@cc.jyu.fi> User-Agent: Mutt/1.4.2.1i X-Bright-Idea: Let's abolish HTML mail! X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on kweetal.tue.nl X-Spam-DCC: : X-Spam-Status: No, hits=-4.9 required=6.3 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Level: cc: freebsd-questions@freebsd.org Subject: Re: Vinum configuration lost at vinum stop / start X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Nov 2004 15:09:51 -0000 --IMjqdzrDRly81ofr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Thu, Nov 11, 2004 at 04:53:39PM +0200, Kim Helenius wrote: > Stijn Hoop wrote: > > I don't know the state of affairs for 5.2.1-RELEASE, but in 5.3-RELEASE= =20 > > gvinum is the way forward. >=20 > Thanks again for answering. Agreed, but there still seems to be a long=20 > way to go. A lot of 'classic' vinum functionality is still missing and=20 > at least for me it still doesn't do the job the way I would find=20 > trustworthy. See below. That's absolutely true. While 5.3 is IMHO pretty stable, gvinum is quite new and therefore a bit less well tested than the rest of the system. Fortunat= ely Lukas Ertl, the maintainer of gvinum, is pretty active and responsive to problems. So if you need a critically stable vinum environment you would be better off with 4.x. > I tested gvinum with some interesting results. First the whole system=20 > froze after creating a concatenated drive and trying to gvinum -rf -r=20 > objects (resetconfig command doesn't exist). That's not good. Nothing in dmesg? If you can consistently get this to happ= en you should send in a problem report. > Next, I created the volume,=20 > newfs, copied some data on it. The rebooted, and issued gvinum start.=20 > > This is what follows: >=20 > 2 drives: > D d1 State: up /dev/ad4s1d A: 285894/286181= =20 > MB (99%) > D d2 State: up /dev/ad5s1d A: 285894/286181= =20 > MB (99%) >=20 > 1 volume: > V vinum0 State: down Plexes: 1 Size: 572 = MB >=20 > 1 plex: > P vinum0.p0 C State: down Subdisks: 2 Size: 572 = MB >=20 > 2 subdisks: > S vinum0.p0.s0 State: stale D: d1 Size: 286 = MB > S vinum0.p0.s1 State: stale D: d2 Size: 286 = MB >=20 > I'm getting a bit confused. Issuing separately 'gvinum start vinum0'=20 > does seem to fix it (all states go 'up') but surely it should come up=20 > fine with just 'gvinum start'? This is how I would start it in loader.con= f. I think I've seen this too, but while testing an other unrelated problem. = At the time I attributed it to other factors. Can you confirm that when you restart again, it stays up? Or maybe try an explicit 'saveconfig' when it is in the 'up' state, and then reboot. > > Have you read > > > >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable= .html > > > > Particularly the 19.2.2 section, 'Staying stable with FreeBSD'? > > >=20 > I have read it and used -stable in 4.x, and if I read it really=20 > carefully I figure out that -stable does not equal "stable" which is way= =20 > I stopped tracking -stable in the first place. And when knowing I would= =20 > only need it to fix raid5 init I'm a bit reluctant to do it as I found=20 > out I can't even create a concat volume correctly. That I can understand. If I may make a polite suggestion, it sounds like you value stability above all else. In this case where vinum is involved, I wou= ld recommend you to stay with 4.x until 5.4 is released. That should take anot= her 6-8 months and probably most of the gvinum issues will have been tackled by then. Although I know that there are a lot of users, myself included, that = run gvinum on 5.x, it is pretty new technology and therefore unfortunately includes pretty new bugs. The other option is to bite the bullet now, and fiddle with gvinum for a few days. Since other users are using it, it is certainly possible. This will take you some time however. It will save you time when the upgrade to 5.4 w= ill be though. It is your decision what part of the tradeoff you like the most. HTH, --Stijn --=20 Apparently, 1 in 5 people in the world are Chinese. And there are 5 people in my family, so it must be one of them. It's either my mum or my dad...... or maybe my older brother John. Or my younger brother Ho-Cha-Chu. But I'm pretty sure it's John. --IMjqdzrDRly81ofr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBk4C8Y3r/tLQmfWcRAqs9AJ9ocFqKWvxpMN7L/q+Ywpynn0gBaQCdGI52 8l1dki8cN70Qrd5yHNVK5Zk= =Y869 -----END PGP SIGNATURE----- --IMjqdzrDRly81ofr--