From owner-freebsd-stable Sat Jun 2 17:48: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 2C79437B422 for ; Sat, 2 Jun 2001 17:47:59 -0700 (PDT) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 42B296ACC0; Sun, 3 Jun 2001 10:17:56 +0930 (CST) Date: Sun, 3 Jun 2001 10:17:56 +0930 From: Greg Lehey To: Steve Price Cc: freebsd-stable@freebsd.org Subject: Re: vinum panic Message-ID: <20010603101756.P87716@wantadilla.lemis.com> References: <20010602121353.N688@bsd.havk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010602121353.N688@bsd.havk.org>; from steve@havk.org on Sat, Jun 02, 2001 at 12:13:53PM -0500 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: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Saturday, 2 June 2001 at 12:13:53 -0500, Steve Price wrote: > I've been trying for several days now to get a RAID5 volume > setup on a new box and no matter what I've tried it always > ends up panic'ing the kernel where I try to create the volume. > > Here's my configuration file: > > drive d1 device /dev/da1s1e > drive d2 device /dev/da2s1e > drive d3 device /dev/da3s1e > drive d4 device /dev/da4s1e > drive d5 device /dev/da5s1e > volume raid > plex org raid5 512k > sd length 17626m drive d1 > sd length 17626m drive d2 > sd length 17626m drive d3 > sd length 17626m drive d4 > sd length 17626m drive d5 > > I've decided that I would skip RAID5 and do RAID10 instead > because I've had success with it before. So after the crash > here's what I did. > > vinum > vinum -> resetconfig > vinum -> saveconfig > vinum -> stop > newfs /dev/da1s1e > newfs /dev/da2s1e > newfs /dev/da3s1e > newfs /dev/da4s1e > newfs /dev/da5s1e So far all of this is unnecessary. > disklabel -e /dev/da1s1e # change 4.2BSD to vinum for 'e' > disklabel -e /dev/da2s1e > disklabel -e /dev/da3s1e > disklabel -e /dev/da4s1e > disklabel -e /dev/da5s1e > vinum > vinum -> mirror -v -n raid10 -s /dev/da2s1e /dev/da3s1e /dev/da4s1e /dev/da5s1e > drive vinumdrive0 device /dev/da2s1e > vinum: drive vinumdrive0 is up > Can't create drive vinumdrive0, device /dev/da2s1e: Invalid argument (22) > vinum -> printconfig > # Vinum configuration of , saved at Sat Jun 2 07:09:00 2001 > vinum -> ls > vinum -> ld > vinum -> lv > vinum -> lp > vinum -> quit > > How can vinumdrive0 be up when it isn't defined? > > Anyone have any pointers to help down the road to vinum nirvana? Well, I'd start off by reading the section DEBUGGING PROBLEMS WITH VINUM in vinum(4), or http://www.vinumvm.org/vinum/how-to-debug.html, or both. Basically, I have almost no information to go on. What was the panic? Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message