Re: Hard drive devices (WAS Need Vinum help)
On Tuesday, 26 August 2003 at 17:54:07 -0700, Thomas Smith wrote: > Thanks to those of you who replied to my previous question. However, I > don't think the problem was Vinum entirely. > > - Is there a way to tell whether a device is aleady configured? That is, > if I'm not sure ad1s1e is configured can I test it to see. vinum ld > - Are / slices mirror-able? There seems to be some conflicting > documentation on this. It's possible. How you do it depends on your version of FreeBSD. > The handbook says yes but www.vinumvm.org, in > some areas, says no--as does freebsddiary.org and daemonnews.org. In other areas, notably http://www.vinumvm.org/cfbsd/vinum.pdf, it says yes. Point me to the others and I'll update them. > - I'm coming from a Redhat background where RAID arrays can be > configured during installation. I understand that this isn't the > case with FreeBSD due to sysinstall limitation. This begs the > question: What is the preferred order of events to setup Vinum? That's in the link above. > I was never able to get both "up" at the same time--one always showed > "Referenced". When I looked in /dev/vinum/drives only a1 would be listed > but not a2. You don't say what version of FreeBSD you were using, but I recently fixed a bug which looks like it could be related to this. Try using /dev/ad0s1a and /dev/ad1s1e and see if you do any better. 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 pgp0.pgp Description: PGP signature
Hard drive devices (WAS Need Vinum help)
Thanks to those of you who replied to my previous question. However, I don't think the problem was Vinum entirely. After doing some research, I discovered that not all /dev devices are created at install time. Looking back, one of the errors I would get when trying to setup Vinum is "device not configured". I haven't been able to find much documentation on what devices are created during the installation. The mirror partition I was trying to setup was on ad1--after I created the slices the BSD slice was ad1s1e. I also had ad1s1d for the swap partition, and (of course) ad1s1c for the drive. Can anyone answer these questions for me: - Is there a way to tell whether a device is aleady configured? That is, if I'm not sure ad1s1e is configured can I test it to see. - Are / slices mirror-able? There seems to be some conflicting documentation on this. The handbook says yes but www.vinumvm.org, in some areas, says no--as does freebsddiary.org and daemonnews.org. - I'm coming from a Redhat background where RAID arrays can be configured during installation. I understand that this isn't the case with FreeBSD due to sysinstall limitation. This begs the question: What is the preferred order of events to setup Vinum? I tried what I found in the docs and couldn't get it done. Generally, I installed FreeBSD. Created my vinum.conf file to concat ad0s1a. Ran "vinum create -f vinum.conf". Saved the changes with "vinum saveconfig". Added the necassary entries to /boot/loader.conf. And rebooted--I was able to get a single vinum drive working fine. I created another config file to add the second drive in a mirrored array. The config files are below. CONFIG 1 drive a1 device /dev/ad0a volume root plex org concat sd length 36g drive a1 CONFIG2 drive a2 device /dev/ad1e volume mirror plex org concat sd length 36g drive a1 plex org concat sd length 36g drive a2 I was never able to get both "up" at the same time--one always showed "Referenced". When I looked in /dev/vinum/drives only a1 would be listed but not a2. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Need Vinum help
Stijn Hoop wrote: On Mon, Aug 25, 2003 at 11:26:48PM -0700, Thomas Smith wrote: The config file is as follows: drive a1 device /dev/ad0a drive a2 device /dev/ad1e You are using slice 'a' on ad0 and slice 'e' on ad1. Typo? No, it's not a typo. When I run "disklabel ad0" the 4.2BSD slice shows as "a". If I do the same for ad1 the 4.2BSD slice shows as "e". (I do, of course change the FStype to vinum.) Is this not typical? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Need Vinum help
On Mon, Aug 25, 2003 at 11:26:48PM -0700, Thomas Smith wrote: > The config file is as follows: > > drive a1 device /dev/ad0a > drive a2 device /dev/ad1e You are using slice 'a' on ad0 and slice 'e' on ad1. Typo? --Stijn -- MY HATE OF D02 KNOW NO LIMIT -- A Silent Wail, http://forum.rpg.net/showthread.php?s=&threadid=31914 pgp0.pgp Description: PGP signature
Re: Need Vinum help
Okay, I'm getting closer. I've got the drives relabeled with a FSType of vinum. Now, I can't seem to get them both up. When I run "vinum create -f /etc/vinum.conf" it creates the a1 drive but shows a2 as "State: referenced". The config file is as follows: drive a1 device /dev/ad0a drive a2 device /dev/ad1e volume root setupstate plex org concat sd length 36g drive a1 plex org concat sd length 36g drive a2 The previous error no longer occurs since I'm now setting the FStype to vinum via disklabel. Greg 'groggy' Lehey wrote: On Monday, 25 August 2003 at 18:19:25 -0700, Thomas Smith wrote: I think I have the process of creating a Vinum volume but I'm missing something. My config file (config1) contains: drive a device /dev/ad0 volume root plex org concat sd length 36g drive a When I run /vinum create config1/ I get the error "Can't initialize device a: Operation not supported by device" I've huffed, and I've puffed, and I've blown over many a page of docs and can't seem to figure out what gives. Try this part of 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 offsetfstype [fsize bsize bps/cpg] a:81920 3440644.2BSD0 0 0 # (Cyl. 240*- 297*) b: 26214481920 swap# (Cyl. 57*- 240*) c: 42267250unused0 0 # (Cyl.0 - 2955*) e:8192004.2BSD0 0 0 # (Cyl.0 - 57*) f: 190 4259844.2BSD0 0 0 # (Cyl. 297*- 1626*) g: 1900741 2325984 vinum0 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. The FStype in /etc/fstab for / is ufs--as I understand it, Vinum needs an FStype of vinum. No. It requires a partition type 'vinum' 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Need Vinum help
On Monday, 25 August 2003 at 18:19:25 -0700, Thomas Smith wrote: > I think I have the process of creating a Vinum volume but I'm missing > something. > > My config file (config1) contains: > > drive a device /dev/ad0 > volume root > plex org concat >sd length 36g drive a > > When I run /vinum create config1/ I get the error "Can't initialize > device a: Operation not supported by device" > > I've huffed, and I've puffed, and I've blown over many a page of docs > and can't seem to figure out what gives. Try this part of 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 offsetfstype [fsize bsize bps/cpg] a:81920 3440644.2BSD0 0 0 # (Cyl. 240*- 297*) b: 26214481920 swap# (Cyl. 57*- 240*) c: 42267250unused0 0 # (Cyl.0 - 2955*) e:8192004.2BSD0 0 0 # (Cyl.0 - 57*) f: 190 4259844.2BSD0 0 0 # (Cyl. 297*- 1626*) g: 1900741 2325984 vinum0 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. > The FStype in /etc/fstab for / is ufs--as I understand it, Vinum > needs an FStype of vinum. No. It requires a partition type 'vinum' 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 pgp0.pgp Description: PGP signature
Need Vinum help
I think I have the process of creating a Vinum volume but I'm missing something. My config file (config1) contains: drive a device /dev/ad0 volume root plex org concat sd length 36g drive a When I run /vinum create config1/ I get the error "Can't initialize device a: Operation not supported by device" I've huffed, and I've puffed, and I've blown over many a page of docs and can't seem to figure out what gives. The FStype in /etc/fstab for / is ufs--as I understand it, Vinum needs an FStype of vinum. I haven't been able to find any docs describing how to make this occur. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
