Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 17 Jun 1999 14:58:46 +0930
From:      Greg Lehey <grog@lemis.com>
To:        Jon Rust <jpr@vcnet.com>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: Vinum stability in 3.2-R
Message-ID:  <19990617145845.K9893@freebie.lemis.com>
In-Reply-To: <v0420511db38e2f0594b5@[209.239.239.22]>; from Jon Rust on Wed, Jun 16, 1999 at 10:07:04PM -0700
References:  <v0420511db38e2f0594b5@[209.239.239.22]>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990617145845.K9893>