[Format recovered--see http://www.lemis.com/email/email-format.html]

Computer output wrapped.

On Thursday, 23 October 2003 at 23:10:01 -0500, [EMAIL PROTECTED] wrote:
> Hello all,
> I have been trying without success to implement a simple vinum
> concatenated RAID system made up of 2 IDE drives.  The boot drive is
> located on another physical drive and is not part of the RAID.
> The problems:
> 1 - I am able to build the RAID, create a filesystem, and mount to a
> directory in the tree. But I am not able to figure out how to add an
> entry to my /etc/fstab file so that it is automatically mounted on
> reboot. I have looked in the handbook and all it says is to "add the
> proper entries".  I simple do not know what entry to add.

Looks like this question has been answered.

> 2 - On reboot, the vinum config is erased. (or at least thats what it
> looks like...see dmesg output for info) It is my understanding that on
> reboot, vinum reads it's configuration from each vinum drive. Since I
> was able to create and mount the RAID, I assume that the configuration
> would still be there on reboot, even thought it is not being mounted
> with fstab (see problem 1). I have tried this on several systems and
> have yet to be successful in having a vinum config survive reboot. I
> have re-read and re-read the vinum section in the handbook and have
> looked elsewhere but have had no luck :(
> Relevent Info:
> I have not made any changes to system or vinum sources. The system is a
> generic 5.1 installed from FTP today.
>> From the box:
> vinum -> l
> 2 drives:
> D a                     State: up       /dev/ad2        A: 981/28629 MB (3%)
> D b                     State: up       /dev/ad3        A: 981/28629 MB (3%)
> 1 volumes:
> V core                  State: up       Plexes:       2 Size:         27 GB
> 2 plexes:
> P core.p0             C State: up       Subdisks:     1 Size:         27 GB
> P core.p1             C State: up       Subdisks:     1 Size:         27 GB
> 2 subdisks:
> S core.p0.s0            State: up       D: a            Size:         27 GB
> S core.p1.s0            State: up       D: b            Size:         27 GB
> #########VINUM CONFIG FILE##########
> thegibsor# cat vinum_config
> drive a device /dev/ad2
> drive b device /dev/ad3

Vinum drives should be partitions, not disks.  This is why Vinum is
not finding anything after 'vinum start'.  From the man page:

     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.

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.

Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to