From owner-freebsd-questions Wed Jun 16 22:29: 4 1999 Delivered-To: freebsd-questions@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 2F8EC14F82 for ; Wed, 16 Jun 1999 22:28:57 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id OAA03220; Thu, 17 Jun 1999 14:58:56 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id OAA44878; Thu, 17 Jun 1999 14:59:01 +0930 (CST) Date: Thu, 17 Jun 1999 14:58:46 +0930 From: Greg Lehey To: Jon Rust Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Vinum stability in 3.2-R Message-ID: <19990617145845.K9893@freebie.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Jon Rust on Wed, Jun 16, 1999 at 10:07:04PM -0700 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 16 June 1999 at 22:07:04 -0700, Jon Rust wrote: > - during set-up the system crashed while in 'vinum' if I issued the > 'start' command (core dump, and auto restart). Issuing the 'start' > command was prolly wrong, but methinks crashing the whole system is a > bad way to tell me that. :-) Indeed. I'd like to take a look at your dump file. > - a few times after configing disks and leaving 'vinum' with a > 'quit', the system would dump core. > > - after finally getting the striped volume up, newfs'd, and mounted, > the system crashed on me when doing a massive file transfer ('tar > cvfp - dir | (cd /newdrive;tar xvfp -)). Unfortunately I'm offsite > now, so I can't see what's on the console-- it did not auto restart > this time through. > > Are there some known issues with vinum and 3.2-R, or did I munge the > config and vinum's really sensitive? It is possible to crash the system if you use really strange configuration commands. This doesn't seem to be what you've been doing--see below. Here's my config: > > bash-2.02# vinum > vinum -> list > Configuration summary > > Drives: 0 (4 configured) > Volumes: 0 (4 configured) > Plexes: 0 (8 configured) > Subdisks: 0 (16 configured) > > > vinum -> drive a device /dev/da0d > vinum -> drive b device /dev/da1d > vinum -> volume mystripe > vinum -> plex org striped 1024k > vinum -> sd length 2040m drive a > vinum -> sd length 2040m drive b This is wrong. I don't even know why it can work, but it's a bug in Vinum to allow this at all. Read vinum(8): vinum requires that all parameters to the create commands must be in a configuration file. Entries in the configuration file define volumes, plexes and subdisks, and may be in free format, except that each entry must be on a single line. The commands you entered should be in the configuration file. You then issue the command vinum -> create configfile to create the objects. See the section HOW TO SET UP VINUM in the man page for more examples. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message