From owner-freebsd-current@FreeBSD.ORG Sat Jan 10 03:00:08 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D524616A4CE for ; Sat, 10 Jan 2004 03:00:08 -0800 (PST) Received: from ozlabs.org (ozlabs.org [203.10.76.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3A3743D2D for ; Sat, 10 Jan 2004 03:00:06 -0800 (PST) (envelope-from grog@lemis.com) Received: from blackwater.lemis.com (blackwater.lemis.com [192.109.197.80]) by ozlabs.org (Postfix) with ESMTP id 62FA52BD5B for ; Sat, 10 Jan 2004 22:00:04 +1100 (EST) Received: by blackwater.lemis.com (Postfix, from userid 1004) id E55D451212; Sat, 10 Jan 2004 21:30:01 +1030 (CST) Date: Sat, 10 Jan 2004 21:30:01 +1030 From: Greg 'groggy' Lehey To: Tim Middleton Message-ID: <20040110110001.GV7617@wantadilla.lemis.com> References: <200401061608.i06G8Gq14706@catwoman.cs.moravian.edu> <200401100021.02691.x@Vex.Net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WMO2RBxtllpoaZld" Content-Disposition: inline In-Reply-To: <200401100021.02691.x@Vex.Net> User-Agent: Mutt/1.4.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: Stephen Corbesero cc: freebsd-current@freebsd.org Subject: Re: is vinum in current working for anyone X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jan 2004 11:00:08 -0000 --WMO2RBxtllpoaZld Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Saturday, 10 January 2004 at 0:21:02 -0500, Tim Middleton wrote: > On Tuesday 06 January 2004 11:08, Stephen Corbesero wrote: >> So, the problem I reported seems to letting vinum load via rc.conf >> and the /etc/rc.d/vinum script. > > Hmm, i've just been experimenting with vinum for the first time this week and > set up a small raid-5 to play with. I had been starting vinum manually after > booting so far, the few times i've rebooted. No problems. > > Just an hour before reading this i'd finally added the start_vinum="YES" to my > rc.conf and rebooted.... after reading this i rushed to "vinum list"... > and ... sure enough, one of the disks from the raid-5 is now is now > "unknown". I'm pretty sure it was okay before that last reboot; though i > can't say 100% for sure. > > Being inexperienced with vinum, not sure how to handle this. Reconfig? > Anyhow, though I can't say for sure the rc.conf startup is what did it... it's > an interesting coincidence. And needless to say... i've removed > start_vinum="YES" from rc.conf just in case. Hmm. There does seem to be some problem in this area. Unfortunately, I've had a lot of interruptions lately, and I'm in a conference all next week, so it's unlikely that I can look at it before next weekend. I'll do that as soon as I can, however. > Below, disk c should be /dev/ad2s1d > > 3 drives: > D b State: up /dev/ad1s3d A: 523/20473 MB (2%) > D a State: up /dev/ad0s2d A: 523/20473 MB (2%) > D c State: referenced unknown A: 0/0 MB As always, http://www.vinumvm.org/vinum/how-to-debug.html tells you what information is needed to follow up on this kind of problem. You could try 'vinum read /dev/ad2s1d' and see what happens. Again, the log information will be of interest, even if there is none :-) Greg -- See complete headers for address and phone numbers. --WMO2RBxtllpoaZld Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE//9sxIubykFB6QiMRAigFAKCMylBqmByqlKwdak02zn/labH+QACgqkl0 67mUnGv5o2QUCJRb4whaKow= =fh23 -----END PGP SIGNATURE----- --WMO2RBxtllpoaZld--