Re: Booting from vinum RAID 1: How should I edit my disk label?
On Tuesday, 30 December 2003 at 21:51:35 -0800, Micheas Herman wrote: > On 31 Dec 03, 4:04PM, Greg 'groggy' Lehey wrote: >> On Sunday, 28 December 2003 at 23:10:20 -0800, Micheas Herman wrote: >>> On Sun, 2003-12-28 at 22:21, Greg 'groggy' Lehey wrote: On Sunday, 28 December 2003 at 20:27:37 -0800, Micheas Herman wrote: > Hi, > 8 partitions: > #size offsetfstype [fsize bsize bps/cpg] > a: 9216000 149667844.2BSD 2048 16384 28552 > b: 20942848 241827844.2BSD 2048 16384 28552 > c: 451265220unused0 0 # "raw" part, don't edit > d: 28672004.2BSD0 0 0 That's wrong. It should be of type Vinum. It also looks very short. >>> >>> It's 138M of a 120G hard drive, which is probably about 60M >>> more than I'll use. (assuming that I don't put more in root than >>> I did with FreeBSD 4.x) >> >> That's a bad assumption, but 138 MB would probably still be enough for >> a root file system. But do you want to put only the root file system >> under Vinum? What's on the rest of this disk? > > Slices that are currenetly working fine under vinum (guess I violated > the golden rule in ignroance) Looks like it. >>> The only downside that i see from reading "The Vinum Volume >>> Manager" is that startup and shutdown will take longer, but I >>> don't see that being much more than a once a month activity at >>> the most. 1-200 days will be a much more frequent time between >>> booting for this system. >> >> And what's the corresponding upside? > > My dump scripts will still work without modification? No, that won't make any difference. It's even possible to correct the configuration on the fly, but it's more pain than I want to describe. > I Guess my problem is that I don't see how to declare an entire disk > a vinum file system and then make subdisks. I may be missing this > in the docs, but i really don't get it. It's pretty basic to the concepts. Have you read the chapter from "The Complete FreeBSD"? If you have, and you still have problems understanding it, I'd appreciate feedback about what's not described adequately. 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
Re: Booting from vinum RAID 1: How should I edit my disk label?
On 31 Dec 03, 4:04PM, Greg 'groggy' Lehey wrote: > On Sunday, 28 December 2003 at 23:10:20 -0800, Micheas Herman wrote: > > On Sun, 2003-12-28 at 22:21, Greg 'groggy' Lehey wrote: > >> On Sunday, 28 December 2003 at 20:27:37 -0800, Micheas Herman wrote: > >>> Hi, > >>> > >>> I am following "13.9.2 Making a Vinum-based Root Volume Accessible to > >>> the Bootstrap" from the FreeBSD Handbook. > >>> > >>> (/dev/vinum/root is mounted at /newroot ) > >>> > >>> ... > >>> Subdisk root.p1.s0: > >>> Size:146664960 bytes (139 MB) > >>> State: up > >>> Plex root.p1 at offset 0 (0 B) > >>> Drive vinumdrive3 (/dev/ad7s1d) at offset 135680 (132 kB) > >> > >> > >>> # disklabel -e /dev/ad7s1 > >>> > >>> gives; > >>> > >>> # /dev/ad7s1: > >>> 8 partitions: > >>> #size offsetfstype [fsize bsize bps/cpg] > >>> a: 9216000 149667844.2BSD 2048 16384 28552 > >>> b: 20942848 241827844.2BSD 2048 16384 28552 > >>> c: 451265220unused0 0 # "raw" part, don't edit > >>> d: 28672004.2BSD0 0 0 > >> > >> That's wrong. It should be of type Vinum. It also looks very short. > > > > It's 138M of a 120G hard drive, which is probably about 60M > > more than I'll use. (assuming that I don't put more in root than > > I did with FreeBSD 4.x) > > That's a bad assumption, but 138 MB would probably still be enough for > a root file system. But do you want to put only the root file system > under Vinum? What's on the rest of this disk? > Slices that are currenetly working fine under vinum (guess I violated the golden rule in ignroance) > >>> e: 4194304 2867204.2BSD 2048 16384 28552 > >>> f: 4194304 44810244.2BSD 2048 16384 28552 > >>> g: 4194304 86753284.2BSD 2048 16384 28552 > >>> h: 2097152 128696324.2BSD 2048 16384 28552 > >>> > >>> I am not sure what my disklabel -e /dev/ad7s1 should look like. > >> > >> That depends on what you're trying to do. I suspect that the entire > >> disk label is bogus. > > > > all my vinum volumes are working fine with two exceptions, 1 the > > swap volume (known problem, at some point in the future I will > > cvsup, make world, etc and it will be fixed, let me know if > > there is any data you would like from this system) and I would > > like to boot from the root volume. which is currently d: > > > > Can I just: > > 1. s/4.2BSD/vinum/ > > Yes. > > > 2. transpose a: and d: > > Well, you can do it, but I don't understand what you're trying to do. > Your "root" partition (a) is much larger than your Vinum drive, and > it's located in a completely different place. > > > (if I do this will I have to rm and recreate the > > volumes? Not a problem I just can't figure it out) > > Again, it depends on what you're trying to do. > > > 3. Do I then just reboot? It would seem that I need to > > install a boot loader some which way. With > > /stand/sysinstall fdisk? or something else? > > You need overlapping partitions, as described in: > > >> Take a look at http://www.vinumvm.org/cfbsd/vinum.pdf and see if that > >> makes any more sense. It's basically trying to tell you the same > >> thing. > > On Sunday, 28 December 2003 at 23:58:33 -0800, Micheas Herman wrote: > > > > Could this be correct for ad6s1 and ad7s1? they are about 20G > > each > > > > a: 9216000 14966784vinum 2048 16384 28552 > > b: 20942848 24182784vinum 2048 16384 28552 > > c: 45126522 0unused 0 0 # "raw" part, > > don't edit > > d: 286439281vinum0 0 0 > >^^^^^ <-changes > > e: 4194304 286720vinum 2048 16384 28552 > > f: 41943044481024vinum 2048 16384 28552 > > g: 41943048675328vinum 2048 16384 28552 > > h: 2097152 12869632vinum 2048 16384 28552 > > No. That's definitely wrong. From the URL above: > > Things you shouldn't do with Vinum > __ > > o Don't put more than one drive on a physical disk. Each drive contains two > copies of the Vinum configuration, and both updating the configuration and > starting Vinum slow down as a result. If you want more than one file system > to occupy space on a physical drive, create subdisks, not drives. > > > # df -h > > FilesystemSize Used Avail Capacity Mounted on > > /dev/ad2s1a 135M54M70M43%/ > > devfs 1.0K 1.0K 0B 100%/dev >
Re: Booting from vinum RAID 1: How should I edit my disk label?
On Sunday, 28 December 2003 at 23:10:20 -0800, Micheas Herman wrote: > On Sun, 2003-12-28 at 22:21, Greg 'groggy' Lehey wrote: >> On Sunday, 28 December 2003 at 20:27:37 -0800, Micheas Herman wrote: >>> Hi, >>> >>> I am following "13.9.2 Making a Vinum-based Root Volume Accessible to >>> the Bootstrap" from the FreeBSD Handbook. >>> >>> (/dev/vinum/root is mounted at /newroot ) >>> >>> ... >>> Subdisk root.p1.s0: >>> Size:146664960 bytes (139 MB) >>> State: up >>> Plex root.p1 at offset 0 (0 B) >>> Drive vinumdrive3 (/dev/ad7s1d) at offset 135680 (132 kB) >> >> >>> # disklabel -e /dev/ad7s1 >>> >>> gives; >>> >>> # /dev/ad7s1: >>> 8 partitions: >>> #size offsetfstype [fsize bsize bps/cpg] >>> a: 9216000 149667844.2BSD 2048 16384 28552 >>> b: 20942848 241827844.2BSD 2048 16384 28552 >>> c: 451265220unused0 0 # "raw" part, don't edit >>> d: 28672004.2BSD0 0 0 >> >> That's wrong. It should be of type Vinum. It also looks very short. > > It's 138M of a 120G hard drive, which is probably about 60M > more than I'll use. (assuming that I don't put more in root than > I did with FreeBSD 4.x) That's a bad assumption, but 138 MB would probably still be enough for a root file system. But do you want to put only the root file system under Vinum? What's on the rest of this disk? >>> e: 4194304 2867204.2BSD 2048 16384 28552 >>> f: 4194304 44810244.2BSD 2048 16384 28552 >>> g: 4194304 86753284.2BSD 2048 16384 28552 >>> h: 2097152 128696324.2BSD 2048 16384 28552 >>> >>> I am not sure what my disklabel -e /dev/ad7s1 should look like. >> >> That depends on what you're trying to do. I suspect that the entire >> disk label is bogus. > > all my vinum volumes are working fine with two exceptions, 1 the > swap volume (known problem, at some point in the future I will > cvsup, make world, etc and it will be fixed, let me know if > there is any data you would like from this system) and I would > like to boot from the root volume. which is currently d: > > Can I just: > 1. s/4.2BSD/vinum/ Yes. > 2. transpose a: and d: Well, you can do it, but I don't understand what you're trying to do. Your "root" partition (a) is much larger than your Vinum drive, and it's located in a completely different place. > (if I do this will I have to rm and recreate the > volumes? Not a problem I just can't figure it out) Again, it depends on what you're trying to do. > 3. Do I then just reboot? It would seem that I need to > install a boot loader some which way. With > /stand/sysinstall fdisk? or something else? You need overlapping partitions, as described in: >> Take a look at http://www.vinumvm.org/cfbsd/vinum.pdf and see if that >> makes any more sense. It's basically trying to tell you the same >> thing. On Sunday, 28 December 2003 at 23:58:33 -0800, Micheas Herman wrote: > > Could this be correct for ad6s1 and ad7s1? they are about 20G > each > > a: 9216000 14966784vinum 2048 16384 28552 > b: 20942848 24182784vinum 2048 16384 28552 > c: 45126522 0unused 0 0 # "raw" part, don't > edit > d: 286439281vinum0 0 0 >^^^^^ <-changes > e: 4194304 286720vinum 2048 16384 28552 > f: 41943044481024vinum 2048 16384 28552 > g: 41943048675328vinum 2048 16384 28552 > h: 2097152 12869632vinum 2048 16384 28552 No. That's definitely wrong. From the URL above: Things you shouldn't do with Vinum __ o Don't put more than one drive on a physical disk. Each drive contains two copies of the Vinum configuration, and both updating the configuration and starting Vinum slow down as a result. If you want more than one file system to occupy space on a physical drive, create subdisks, not drives. > # df -h > FilesystemSize Used Avail Capacity Mounted on > /dev/ad2s1a 135M54M70M43%/ > devfs 1.0K 1.0K 0B 100%/dev > /dev/vinum/home90G12K83G 0%/home > /dev/vinum/tmp4.3G 3.4M 3.9G 0%/tmp > /dev/vinum/usr1.9G 954M 866M52%/usr > /dev/vinum/usrports 1.9G 516M 1.3G28%/usr/ports > /dev/vinum/usrlocal 1.9G71M 1.7G 4%/usr/local > /dev/vinum/var9.7G
Re: Booting from vinum RAID 1: How should I edit my disk label?
On Sun, 2003-12-28 at 23:10, Micheas Herman wrote: > On Sun, 2003-12-28 at 22:21, Greg 'groggy' Lehey wrote: > > On Sunday, 28 December 2003 at 20:27:37 -0800, Micheas Herman wrote: > > > Hi, > > > > > > I am following "13.9.2 Making a Vinum-based Root Volume Accessible to > > > the Bootstrap" from the FreeBSD Handbook. > > > > > > (/dev/vinum/root is mounted at /newroot ) > > > > > > ... > > > Subdisk root.p1.s0: > > > Size:146664960 bytes (139 MB) > > > State: up > > > Plex root.p1 at offset 0 (0 B) > > > Drive vinumdrive3 (/dev/ad7s1d) at offset 135680 (132 kB) > > > > > > > # disklabel -e /dev/ad7s1 > > > > > > gives; > > > > > > # /dev/ad7s1: > > > 8 partitions: > > > #size offsetfstype [fsize bsize bps/cpg] > > > a: 9216000 149667844.2BSD 2048 16384 28552 > > > b: 20942848 241827844.2BSD 2048 16384 28552 > > > c: 451265220unused0 0 # "raw" part, don't edit > > > d: 28672004.2BSD0 0 0 > > > > That's wrong. It should be of type Vinum. It also looks very short. > Could this be correct for ad6s1 and ad7s1? they are about 20G each a: 9216000 14966784vinum 2048 16384 28552 b: 20942848 24182784vinum 2048 16384 28552 c: 45126522 0unused 0 0 # "raw" part, don't edit d: 286439281vinum0 0 0 ^^^^^ <-changes e: 4194304 286720vinum 2048 16384 28552 f: 41943044481024vinum 2048 16384 28552 g: 41943048675328vinum 2048 16384 28552 h: 2097152 12869632vinum 2048 16384 28552 # df -h FilesystemSize Used Avail Capacity Mounted on /dev/ad2s1a 135M54M70M43%/ devfs 1.0K 1.0K 0B 100%/dev /dev/vinum/home90G12K83G 0%/home /dev/vinum/tmp4.3G 3.4M 3.9G 0%/tmp /dev/vinum/usr1.9G 954M 866M52%/usr /dev/vinum/usrports 1.9G 516M 1.3G28%/usr/ports /dev/vinum/usrlocal 1.9G71M 1.7G 4%/usr/local /dev/vinum/var9.7G 1.0M 8.9G 0%/var /dev/vinum/root 135M54M70M44%/newroot The only downside that i see from reading "The Vinum Volume Manager" is that startup and shutdown will take longer, but I don't see that being much more than a once a month activity at the most. 1-200 days will be a much more frequent time between booting for this system. > It's 138M of a 120G hard drive, which is probably about 60M > more than I'll use. (assuming that I don't put more in root than > I did with FreeBSD 4.x) > > > > > > e: 4194304 2867204.2BSD 2048 16384 28552 > > > f: 4194304 44810244.2BSD 2048 16384 28552 > > > g: 4194304 86753284.2BSD 2048 16384 28552 > > > h: 2097152 128696324.2BSD 2048 16384 28552 > > > > -- Micheas Herman email: [EMAIL PROTECTED] Free Print Shop web: http://www.FreePrintShop.org phone: (415)648-3222fax: (415)648-3222 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting from vinum RAID 1: How should I edit my disk label?
On Sun, 2003-12-28 at 22:21, Greg 'groggy' Lehey wrote: > On Sunday, 28 December 2003 at 20:27:37 -0800, Micheas Herman wrote: > > Hi, > > > > I am following "13.9.2 Making a Vinum-based Root Volume Accessible to > > the Bootstrap" from the FreeBSD Handbook. > > > > (/dev/vinum/root is mounted at /newroot ) > > > > ... > > Subdisk root.p1.s0: > > Size:146664960 bytes (139 MB) > > State: up > > Plex root.p1 at offset 0 (0 B) > > Drive vinumdrive3 (/dev/ad7s1d) at offset 135680 (132 kB) > > > > # disklabel -e /dev/ad7s1 > > > > gives; > > > > # /dev/ad7s1: > > 8 partitions: > > #size offsetfstype [fsize bsize bps/cpg] > > a: 9216000 149667844.2BSD 2048 16384 28552 > > b: 20942848 241827844.2BSD 2048 16384 28552 > > c: 451265220unused0 0 # "raw" part, don't edit > > d: 28672004.2BSD0 0 0 > > That's wrong. It should be of type Vinum. It also looks very short. It's 138M of a 120G hard drive, which is probably about 60M more than I'll use. (assuming that I don't put more in root than I did with FreeBSD 4.x) > > > e: 4194304 2867204.2BSD 2048 16384 28552 > > f: 4194304 44810244.2BSD 2048 16384 28552 > > g: 4194304 86753284.2BSD 2048 16384 28552 > > h: 2097152 128696324.2BSD 2048 16384 28552 > > > > I am not sure what my disklabel -e /dev/ad7s1 should look like. > > That depends on what you're trying to do. I suspect that the entire > disk label is bogus. all my vinum volumes are working fine with two exceptions, 1 the swap volume (known problem, at some point in the future I will cvsup, make world, etc and it will be fixed, let me know if there is any data you would like from this system) and I would like to boot from the root volume. which is currently d: Can I just: 1. s/4.2BSD/vinum/ 2. transpose a: and d: (if I do this will I have to rm and recreate the volumes? Not a problem I just can't figure it out) 3. Do I then just reboot? It would seem that I need to install a boot loader some which way. With /stand/sysinstall fdisk? or something else? > > Take a look at http://www.vinumvm.org/cfbsd/vinum.pdf and see if that > makes any more sense. It's basically trying to tell you the same > thing. Thanks, I've printed it out and will read it over. (probably many times) Micheas > > 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. -- Micheas Herman email: [EMAIL PROTECTED] Free Print Shop web: http://www.FreePrintShop.org phone: (415)648-3222fax: (415)648-3222 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting from vinum RAID 1: How should I edit my disk label?
On Sun, 2003-12-28 at 20:27, Micheas Herman wrote: > Hi, > > I am following "13.9.2 Making a Vinum-based Root Volume Accessible to > the Bootstrap" from the FreeBSD Handbook. > > Here is where I am at: > > (/dev/vinum/root is mounted at /newroot ) > > # cat /newroot/boot/loader.conf > # the following two lines so we can boot from vinum. > > vinum_load="YES" > vinum.autostart="YES" > > > # vinum l -rv root > Volume root:Size: 146664960 bytes (139 MB) > State: up > Flags: open > 2 plexes > Read policy: round robin > Plex root.p0: Size: 146664960 bytes (139 MB) > Subdisks:1 > State: up > Organization: concat > Part of volume root > > Plex root.p1: Size: 146664960 bytes (139 MB) > Subdisks:1 > State: up > Organization: concat > Part of volume root > > Subdisk root.p0.s0: > Size:146664960 bytes (139 MB) > State: up > Plex root.p0 at offset 0 (0 B) > Drive vinumdrive2 (/dev/ad6s1d) at offset 135680 (132 kB) > > Subdisk root.p1.s0: > Size:146664960 bytes (139 MB) > State: up > Plex root.p1 at offset 0 (0 B) > Drive vinumdrive3 (/dev/ad7s1d) at offset 135680 (132 kB) > > > > # disklabel -e /dev/ad7s1 > > gives; > > # /dev/ad7s1: > 8 partitions: > #size offsetfstype [fsize bsize bps/cpg] > a: 9216000 149667844.2BSD 2048 16384 28552 > b: 20942848 241827844.2BSD 2048 16384 28552 > c: 451265220unused0 0 # "raw" part, don't edit > d: 28672004.2BSD0 0 0 > e: 4194304 2867204.2BSD 2048 16384 28552 > f: 4194304 44810244.2BSD 2048 16384 28552 > g: 4194304 86753284.2BSD 2048 16384 28552 > h: 2097152 128696324.2BSD 2048 16384 28552 > > > I am not sure what my disklabel -e /dev/ad7s1 should look like. Replying to my own post. Do I need to change partitions "a:" (currently part of volume tmp) and "d:" (currently part of volume root) Also with this configuration do I need to shrink the size of any of my partitions. (I am unclear as to if I have 8k at the beginning of the drive) I can delete my current d: partition and make it smaller if that is needed. I just don't grok this yet :-( thanks again for any help. Micheas -- Micheas Herman email: [EMAIL PROTECTED] Free Print Shop web: http://www.FreePrintShop.org phone: (415)648-3222fax: (415)648-3222 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting from vinum RAID 1: How should I edit my disk label?
On Sunday, 28 December 2003 at 20:27:37 -0800, Micheas Herman wrote: > Hi, > > I am following "13.9.2 Making a Vinum-based Root Volume Accessible to > the Bootstrap" from the FreeBSD Handbook. > > (/dev/vinum/root is mounted at /newroot ) > > ... > Subdisk root.p1.s0: > Size:146664960 bytes (139 MB) > State: up > Plex root.p1 at offset 0 (0 B) > Drive vinumdrive3 (/dev/ad7s1d) at offset 135680 (132 kB) > # disklabel -e /dev/ad7s1 > > gives; > > # /dev/ad7s1: > 8 partitions: > #size offsetfstype [fsize bsize bps/cpg] > a: 9216000 149667844.2BSD 2048 16384 28552 > b: 20942848 241827844.2BSD 2048 16384 28552 > c: 451265220unused0 0 # "raw" part, don't edit > d: 28672004.2BSD0 0 0 That's wrong. It should be of type Vinum. It also looks very short. > e: 4194304 2867204.2BSD 2048 16384 28552 > f: 4194304 44810244.2BSD 2048 16384 28552 > g: 4194304 86753284.2BSD 2048 16384 28552 > h: 2097152 128696324.2BSD 2048 16384 28552 > > I am not sure what my disklabel -e /dev/ad7s1 should look like. That depends on what you're trying to do. I suspect that the entire disk label is bogus. Take a look at http://www.vinumvm.org/cfbsd/vinum.pdf and see if that makes any more sense. It's basically trying to tell you the same thing. 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
Booting from vinum RAID 1: How should I edit my disk label?
Hi, I am following "13.9.2 Making a Vinum-based Root Volume Accessible to the Bootstrap" from the FreeBSD Handbook. Here is where I am at: (/dev/vinum/root is mounted at /newroot ) # cat /newroot/boot/loader.conf # the following two lines so we can boot from vinum. vinum_load="YES" vinum.autostart="YES" # vinum l -rv root Volume root:Size: 146664960 bytes (139 MB) State: up Flags: open 2 plexes Read policy: round robin Plex root.p0: Size: 146664960 bytes (139 MB) Subdisks:1 State: up Organization: concat Part of volume root Plex root.p1: Size: 146664960 bytes (139 MB) Subdisks:1 State: up Organization: concat Part of volume root Subdisk root.p0.s0: Size:146664960 bytes (139 MB) State: up Plex root.p0 at offset 0 (0 B) Drive vinumdrive2 (/dev/ad6s1d) at offset 135680 (132 kB) Subdisk root.p1.s0: Size:146664960 bytes (139 MB) State: up Plex root.p1 at offset 0 (0 B) Drive vinumdrive3 (/dev/ad7s1d) at offset 135680 (132 kB) # disklabel -e /dev/ad7s1 gives; # /dev/ad7s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 9216000 149667844.2BSD 2048 16384 28552 b: 20942848 241827844.2BSD 2048 16384 28552 c: 451265220unused0 0 # "raw" part, don't edit d: 28672004.2BSD0 0 0 e: 4194304 2867204.2BSD 2048 16384 28552 f: 4194304 44810244.2BSD 2048 16384 28552 g: 4194304 86753284.2BSD 2048 16384 28552 h: 2097152 128696324.2BSD 2048 16384 28552 I am not sure what my disklabel -e /dev/ad7s1 should look like. Any help would be appreciated. I don't want to redo the last seven hours of setting up this server. (mostly waiting on gcc but still,) Micheas -- Micheas Herman email: [EMAIL PROTECTED] Free Print Shop web: http://www.FreePrintShop.org phone: (415)648-3222fax: (415)648-3222 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
