Re: bootvinum and multiple pc-partitions
On Thursday, 19 December 2002 at 22:34:57 -0600, Hari Bhaskaran wrote: > On Fri, Dec 20, 2002 at 02:26:34PM +1030, Greg 'groggy' Lehey wrote: > >> I must confess to being a bit baffled. You seem to be confused on a >> number of points. Certainly there's never any reason to put more than >> one Vinum volume on a physical disk. > > Are you asking where the second hard-drive is attached to the same > cable? No. > Yes, one is the master, other is slave. I guess this could be > problem if the master is dead. But they are still two separate > harddisks. /dev/ad1s1 and /dev/ad1s2 are both the same disk. > I was following the article > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/vinum/index.html > > After a search, I found some other articles > http://org.netbase.org/vinum-mirrored.html. May be I will try to > follow this one. > > Here is a summary of what I was trying to do:- > > I began a normal FreeBSD install with a single 120G disk. I needed the > following partitions > > / 1G > swap6G (may be a bit too much!) > /var3G > /var/log 1G > /var/tmp 1G > /tmp3G > /usr3G > /usr/home 3G > /fs12G > /fs220G > /fs340G > /fs431G > > Since I don't seem to be able to create more than 7 or so FreeBSD > fs partitions per PC-partition, I split the PC-partition into two. > That's why I have ad0s1 & ad0s2. You don't need more than one partition. > Now I need the whole disk mirrored on the second 120G disk. I may > not want to mirror /fs4, that's all. > >> create.ThruBank >> create.YouCrazy > > There are default files (I didn't care to change the default names) > generated by bootvinum. > >> You shouldn't be specifying explicit drive offsets. It's also not a >> good idea to specify names for pleses or subdisks. In addition, >> you've detected a bug in the Vinum parser: you can't have / characters >> in object names. > [snip] >> >> You're creating a lot of unattached plexes here. Why? > > I just ran the script. So please ignore these. > >> I don't know why you're going to so much trouble when it's *much* >> easier to do it manually. I can't help you with bootvinum, beyond >> to suggest not to use it. I can only repeat that. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: bootvinum and multiple pc-partitions
On Fri, Dec 20, 2002 at 02:26:34PM +1030, Greg 'groggy' Lehey wrote: > I must confess to being a bit baffled. You seem to be confused on a > number of points. Certainly there's never any reason to put more than > one Vinum volume on a physical disk. Are you asking where the second hard-drive is attached to the same cable? Yes, one is the master, other is slave. I guess this could be problem if the master is dead. But they are still two separate harddisks. I was following the article http://www.freebsd.org/doc/en_US.ISO8859-1/articles/vinum/index.html After a search, I found some other articles http://org.netbase.org/vinum-mirrored.html. May be I will try to follow this one. Here is a summary of what I was trying to do:- I began a normal FreeBSD install with a single 120G disk. I needed the following partitions / 1G swap 6G (may be a bit too much!) /var 3G /var/log 1G /var/tmp 1G /tmp 3G /usr 3G /usr/home 3G /fs1 2G /fs2 20G /fs3 40G /fs4 31G Since I don't seem to be able to create more than 7 or so FreeBSD fs partitions per PC-partition, I split the PC-partition into two. That's why I have ad0s1 & ad0s2. Now I need the whole disk mirrored on the second 120G disk. I may not want to mirror /fs4, that's all. > create.ThruBank > create.YouCrazy There are default files (I didn't care to change the default names) generated by bootvinum. > You shouldn't be specifying explicit drive offsets. It's also not a > good idea to specify names for pleses or subdisks. In addition, > you've detected a bug in the Vinum parser: you can't have / characters > in object names. [snip] > > You're creating a lot of unattached plexes here. Why? I just ran the script. So please ignore these. > > I don't know why you're going to so much trouble when it's *much* > easier to do it manually. I can't help you with bootvinum, beyond to > suggest not to use it. > > Greg > -- > See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: bootvinum and multiple pc-partitions
On Thursday, 19 December 2002 at 21:33:50 -0600, Hari Bhaskaran wrote: > Hi, > > I am having a problem using the bootvinum script. It seems to > consider only the first slice (PC-partition) of the root > spindle. I have put all vinum related files > here http://65.189.239.65/vinum_files/ > > I have two (1 when you consider vinum) 120G dsks that need to be > split onto more than 12 fs's. I created two PC-partitions 60G > each to get over the a to h partition limit. I must confess to being a bit baffled. You seem to be confused on a number of points. Certainly there's never any reason to put more than one Vinum volume on a physical disk. I've taken a look at http://65.189.239.65/vinum_files/bootvinum/ (what happened to your DNS?), and find: bootvinum I've never seen this before. I don't do perl, but it doesn't seem like it does anything useful. create.ThruBank drive ThruBank device /dev/ad1s2h It's not clear what use this is by itself. create.YouCrazy drive YouCrazy device /dev/ad0s1h volume fs3 plex name fs3.p0 org concat volume fs3 sd name fs3.p0.s0 drive YouCrazy plex fs3.p0 len 88066257s driveoffset 16777481s volume var plex name var.p0 org concat volume var sd name var.p0.s0 drive YouCrazy plex var.p0 len 6291456s driveoffset 265s volume var/tmp plex name var/tmp.p0 org concat volume var/tmp sd name var/tmp.p0.s0 drive YouCrazy plex var/tmp.p0 len 2097152s driveoffset 6291721s volume var/log plex name var/log.p0 org concat volume var/log sd name var/log.p0.s0 drive YouCrazy plex var/log.p0 len 2097152s driveoffset 8388873s volume tmp plex name tmp.p0 org concat volume tmp sd name tmp.p0.s0 drive YouCrazy plex tmp.p0 len 6291456s driveoffset 10486025s You shouldn't be specifying explicit drive offsets. It's also not a good idea to specify names for pleses or subdisks. In addition, you've detected a bug in the Vinum parser: you can't have / characters in object names. create.UpWindow drive UpWindow device /dev/ad1s1h plex name fs3.p1 org concat volume fs3 sd name fs3.p1.s0 drive UpWindow plex fs3.p1 len 88066257s driveoffset 16777481s plex name var.p1 org concat volume var sd name var.p1.s0 drive UpWindow plex var.p1 len 6291456s driveoffset 265s plex name var/tmp.p1 org concat volume var/tmp sd name var/tmp.p1.s0 drive UpWindow plex var/tmp.p1 len 2097152s driveoffset 6291721s plex name var/log.p1 org concat volume var/log sd name var/log.p1.s0 drive UpWindow plex var/log.p1 len 2097152s driveoffset 8388873s plex name tmp.p1 org concat volume tmp sd name tmp.p1.s0 drive UpWindow plex tmp.p1 len 6291456s driveoffset 10486025s You're creating a lot of unattached plexes here. Why? disklabel.ad0s1 disklabel.ad0s1.b4vinum disklabel.ad1s1 disklabel.ad1s1.b4vinum disklabel.ad1s2 disklabel.ad1s2.b4vinum These look like normal enough volume labels, though it's not clear why you have ad1s2. > I also have a different kind of problem. I was trying to find out > how to modify bootvinum script to skip certain partitions when it > processes /etc/fstab to create /etc/fstab.vinum I have two disks, > and I want certain "critical" partitions mirrored on both, but I > want each disk to have its own partitions made out of remaining > space in each. > > I realise this may a little too much for the bootvinum perl script, > but I just wanted to find out before I modify anything or try the > manual approach. I don't know why you're going to so much trouble when it's *much* easier to do it manually. I can't help you with bootvinum, beyond to suggest not to use it. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message