Vinum

[Greg 'groggy' Lehey]

On Friday, 26 December 2003 at 15:16:38 +0100, MarciOnMaillist at web.de wrote:
> hello folks, i have a little problem with my vinum on
> -> FreeBSD 5.1
>
> i wanted to create an LogVol with vinum. I have 4 physikal hard drives
> in my pc. and i wanted to combine 3 of them with vinum.
> After i have read the handbook and the manpages i configured my vinum
> without problems, but after restart all my configs are lost.
> Here are the steps I've done:
>
> touch /etc/vinum.conf
> -> vinum create -f -v /etc/vinum.conf
>
> In this file there are these entrys:
>
>    drive d1 device /dev/ad1s1
>    drive d2 device /dev/ad2s1
>    drive d3 device /dev/ad3s1

These are slices, not partitions.  From the man page:

DRIVE LAYOUT CONSIDERATIONS
     vinum drives are currently BSD disk partitions.  They must be of type
     vinum in order to avoid overwriting data used for other purposes.  Use
     disklabel -e to edit a partition type definition.  The following display
     shows a typical partition layout as shown by disklabel(8):

     8 partitions:
     #        size   offset    fstype   [fsize bsize bps/cpg]
       a:    81920   344064    4.2BSD        0     0     0   # (Cyl.  240*- 297*)
       b:   262144    81920      swap                        # (Cyl.   57*- 240*)
       c:  4226725        0    unused        0     0         # (Cyl.    0 - 2955*)
       e:    81920        0    4.2BSD        0     0     0   # (Cyl.    0 - 57*)
       f:  1900000   425984    4.2BSD        0     0     0   # (Cyl.  297*- 1626*)
       g:  1900741  2325984     vinum        0     0     0   # (Cyl. 1626*- 2955*)

     In this example, partition ``g'' may be used as a vinum partition.  Par-
     titions ``a'', ``e'' and ``f'' may be used as UFS file systems or ccd
     partitions.  Partition ``b'' is a swap partition, and partition ``c''
     represents the whole disk and should not be used for any other purpose.

>    volume doc1s1 setupstate
>       plex org concat
>          sd length 0 drive d1
>          sd length 0 drive d2
>          sd lenght 0 drive d3
>
>
> after I did this, all plexes are up without errors.

Yes, this is a bug.  You shouldn't be able to do this.

> then I did:
>
> -> newfs /dev/vinum/doc1s1
> -> disklabel -e /dev/vinum/doc1s1

You shouldn't run disklabel on the volume.  Run it on /dev/ad1s1,
/dev/ad2s1 and /dev/ad3s1 instead.  Then create drives on, say,
/dev/ad1s1g, /dev/ad2s1g and /dev/ad3s1g, modify your configuration
file, and all should be well.

Greg
--
When replying to this message, please copy the original recipients.
If you don't, I may ignore the reply or reply to the original recipients.
For more information, see http://www.lemis.com/questions.html
See complete headers for address and phone numbers.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20031227/f741cf2e/attachment.bin