From owner-freebsd-current@FreeBSD.ORG Fri Jan 9 21:21:17 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 5799D16A4CE; Fri, 9 Jan 2004 21:21:17 -0800 (PST) Received: from smaug.vex.net (smaug.vex.net [66.246.136.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id D760643D58; Fri, 9 Jan 2004 21:21:13 -0800 (PST) (envelope-from x@xxvii.net) Received: from bee.vii.net (69-90-55-67.fastdsl.ca [69.90.55.67]) by smaug.vex.net (Postfix) with ESMTP id C87C44861C; Sat, 10 Jan 2004 00:21:14 -0500 (EST) Received: by bee.vii.net (Postfix, from userid 1000) id 5BC57B964; Sat, 10 Jan 2004 00:21:04 -0500 (EST) From: Tim Middleton Organization: xxvii.net To: freebsd-current@freebsd.org Date: Sat, 10 Jan 2004 00:21:02 -0500 User-Agent: KMail/1.5.94 References: <200401061608.i06G8Gq14706@catwoman.cs.moravian.edu> In-Reply-To: <200401061608.i06G8Gq14706@catwoman.cs.moravian.edu> X-Whee: Yes, Please. MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200401100021.02691.x@Vex.Net> cc: Stephen Corbesero cc: Greg 'groggy' Lehey 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 05:21:17 -0000 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. 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 1 volumes: V raid5 State: up Plexes: 1 Size: 38 GB 1 plexes: P raid5.p0 R5 State: degraded Subdisks: 3 Size: 38 GB 3 subdisks: S raid5.p0.s0 State: up D: a Size: 19 GB S raid5.p0.s1 State: up D: b Size: 19 GB S raid5.p0.s2 State: crashed D: c Size: 19 GB -- Tim Middleton | Cain Gang Ltd | Then suddenly, for no apparent reason, the x@veX.net | www.Vex.Net | unpittying orchestra struck up a polka. -D