Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 3 Apr 2001 15:39:15 +0930
From:      Greg Lehey <grog@lemis.com>
To:        Wency Arzadon <wency@juniper.net>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: newbie - vinum
Message-ID:  <20010403153915.R71213@wantadilla.lemis.com>
In-Reply-To: <3AC95B82.AAFE52A2@juniper.net>; from wency@juniper.net on Mon, Apr 02, 2001 at 10:11:30PM -0700
References:  <3AC95B82.AAFE52A2@juniper.net>

next in thread | previous in thread | raw e-mail | index | archive | help
[Format recovered--see http://www.lemis.com/email/email-format.html]

Your mailer wraps output lines.

On Monday,  2 April 2001 at 22:11:30 -0700, Wency Arzadon wrote:
> Hi All,
>
> I'm new to Freebsd; I'm trying to use
> vinum to mirror a bsd box, running 4.2REL
> with 2 internal IDE drives that are both identical.
>
> My goal is to have a mirrored root drive which contain
> the following partitions, and I'm not sure if its possible
> to do this. I'm familiar with Veritas, but unsure how vinum
> tries to do this. How it tries to do encapsulation of the root drive
> etc..

It doesn't.  This is currently not possible.

> I've compiled vinum in the kernel..

From the man page:

     It is possible to configure vinum in the kernel, but this is not recom-
     mended.

> I'm getting some weird errors along with different
> scenarios.
>
> Below are my two drives:
> host# fdisk -s /dev/ad1
> /dev/ad1: 3737 cyl 255 hd 63 sec
> Part        Start        Size Type Flags
>    1:          63     8177022 0xa5 0x80
>    2:     8177085     1012095 0xa5 0x80
>    3:     9189180     1012095 0xa5 0x80
>    4:    10201275    49833630 0xa5 0x80
>
> host# fdisk -s /dev/ad0
> /dev/ad0: 38118 cyl 25 hd 63 sec
> Part        Start        Size Type Flags
>    1:          63     8191512 0xa5 0x80
>    2:     8191575     2047500 0xa5 0x00
>    3:    10239075     1023750 0xa5 0x00
>    4:    11262825    48773025 0xa5 0x00

Given the problems you have, the output of disklabel would be more
interesting.  But you almost never need multiple FreeBSD partitions on
a disk.  There are exceptions, but I can't see any reason here.

> ------
> /dev/ad0 is my current OS partition.
> Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
> /dev/ad0s1a   3969738   358984  3293175    10%    /
> /dev/ad0s4e  23635524        1 21744682     0%    /export/home
> /dev/ad0s3e    495986     4287   452021     1%    /var
> ------
> I've tried configuring different ways, below is where
> i'm using config file.
>
> My config file:/etc/vinum/config
> gnosis# cat /etc/vinum/config
> # Vinum configuration of gnosis.englab.juniper.net, saved at Thu Mar 29
> 18:16:11 2001
>
> drive vinumdrive0 device /dev/ad1a
> drive vinumdrive1 device /dev/ad1b
> drive vinumdrive2 device /dev/ad1d
> drive vinumdrive3 device /dev/ad1e

This is wrong.  You should never put more than one drive on a spindle.

> volume rootmirror
>  plex org concat
>   sd length 2g drive vinumdrive0
>
> volume swapmirror
>  plex org concat
>   sd length 1000M drive vinumdrive1
>
> volume varmirror
>  plex org concat
>   sd length 500m drive vinumdrive2
>
> volume dbmirror
>  plex org concat
>   sd length 23g drive vinumdrive3

Under these circumstances, put all the subdisks on the same drive.
But note that the names are wrong: these volumes are not mirrored.

> -----
> vinum -> create -f /etc/vinum/config
>    3: drive vinumdrive0 device /dev/ad1a
> ** 3 : Invalid argument

This looks like you haven't set the partition to type 'vinum'.  That
should show up in your log files.

>    4: drive vinumdrive1 device /dev/ad1b
> ** 4 : Invalid argument
>    5: drive vinumdrive2 device /dev/ad1d
> ** 5 : Invalid argument
>    6: drive vinumdrive3 device /dev/ad1e
> ** 6 : Invalid argument
> 0 drives:
> vinum ->
> ----
> vinum -> init rootmirror.p0.s0
> vinum -> vinum[266]: initializing subdisk /dev/vinum/sd/rootmirror.p0.s0
> Can't initialize /dev/vinum/sd/rootmirror.p0.s0: Device busy (16)

Considering that the subdisk is down, this isn't going to work.  I'll
check why it says "device busy" and not "I/O error".

> Why does it complained  with invalid agument?
> How do I initialize my drives, subdisk?

You don't need to for this kind.  But first you get the devices up.

> It eventually all become in the State: up after mucking around.

I'd be interested how.

> Anyways the man pages for vinum is not too intuitive.  Once i try
> newfs/or mounting my machine crashes.

More details, please.  How did you get it up?  Where are the dumps?

> Can someone point to some good doc, or tell me I cannot do this with
> IDE drives.

You can do this with IDE drives.  Solve the first problem first, and
the rest will probably be OK.  If you still have problems, look at
http://www.vinumvm.org/vinum/how-to-debug.html.

Greg
--
When replying to this message, please copy the original recipients.
If you don't, I may ignore the reply.
For more information, see http://www.lemis.com/questions.html
Finger grog@lemis.com for PGP public key
See complete headers for address and phone numbers

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?20010403153915.R71213>