Re: vinum, RAID-5, newfs

From: Greg 'groggy' Lehey <grog(at)>
Date: Fri, 3 Oct 2003 09:03:07 +0930

On Friday, 3 October 2003 at 0:23:13 +0200, Oliver Lehmann wrote:
> Hallo,
> nun habe ich mir mal etwas Zeit genommen das schon laenger geplante RAID5
> mit vinum an den Start zu bringen. Irgendwie komm ich aber nicht weit.
> Hier erstmal die Sysconfig.
> Soweit so gut...
> root(at)nudel /root> cat /etc/vinum.conf
> drive d1 device /dev/da1s1
> drive d2 device /dev/da2s1
> drive d3 device /dev/da3s1
> drive d4 device /dev/da4s1
> drive d5 device /dev/da5s1


     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.

     The vinum utility uses the first 265 sectors on each partition for con-
     figuration information, so the maximum size of a subdisk is 265 sectors
     smaller than the drive.

Ich kann mir nur vorstellen, dass Du auf jeder Platte auch eine
Partition hast, die die gesamte Scheibe belegt.

> vinum -> create /etc/vinum.conf
> 5 drives:
> D d1 State: up /dev/da1s1 A: 0/1004 MB (0%)
> D d2 State: up /dev/da2s1 A: 0/1005 MB (0%)
> D d3 State: up /dev/da3s1 A: 0/1005 MB (0%)
> D d4 State: up /dev/da4s1 A: 0/1005 MB (0%)
> D d5 State: up /dev/da5s1 A: 0/1005 MB (0%)

Was sagt printconfig?

> sd length 1004m drive d1
> sd length 1005m drive d2
> sd length 1005m drive d3
> sd length 1005m drive d4
> sd length 1005m drive d5

Die Subdisks müssen alle die gleiche Länge haben. Vinum soll das
merken und den restlichen Platz wieder freigeben, allerdings fürchte
ich, dass damit unentdeckte Lücken entstehen können. Schau' mal die
Ausgabe von 'ls -v' an. Sind dort Lücken?


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
See complete headers for address and phone numbers.
NOTE: Due to the currently active Microsoft-based worms, I am limiting
all incoming mail to 131,072 bytes.  This is enough for normal mail,
but not for large attachments.  Please send these as URLs.

To Unsubscribe: send mail to
with "unsubscribe de-bsd-questions" in the body of the message
Received on Fri 03 Oct 2003 - 01:33:56 CEST

search this site