Date: Wed, 31 Dec 2003 16:04:00 +1030 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: Micheas Herman <micheas@freep.org> Cc: freebsd-questions@freebsd.org Subject: Re: Booting from vinum RAID 1: How should I edit my disk label? Message-ID: <20031231053400.GO10758@wantadilla.lemis.com> In-Reply-To: <1072684712.1411.97.camel@tux> <1072681819.1411.65.camel@tux> References: <1072672057.1411.22.camel@tux> <20031229062145.GB10758@wantadilla.lemis.com> <1072681819.1411.65.camel@tux> <1072684712.1411.97.camel@tux> <1072672057.1411.22.camel@tux> <20031229062145.GB10758@wantadilla.lemis.com> <1072681819.1411.65.camel@tux>
next in thread | previous in thread | raw e-mail | index | archive | help
--J/pvEKOcHgREgBce Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 offset fstype [fsize bsize bps/cpg] >>> a: 9216000 14966784 4.2BSD 2048 16384 28552 >>> b: 20942848 24182784 4.2BSD 2048 16384 28552 >>> c: 45126522 0 unused 0 0 # "raw" part, don't edit >>> d: 286720 0 4.2BSD 0 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 286720 4.2BSD 2048 16384 28552 >>> f: 4194304 4481024 4.2BSD 2048 16384 28552 >>> g: 4194304 8675328 4.2BSD 2048 16384 28552 >>> h: 2097152 12869632 4.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 14966784 vinum 2048 16384 28552 > b: 20942848 24182784 vinum 2048 16384 28552 > c: 45126522 0 unused 0 0 # "raw" part, don't edit > d: 286439 281 vinum 0 0 0 > ^^^^^^ ^^^ <-changes > e: 4194304 286720 vinum 2048 16384 28552 > f: 4194304 4481024 vinum 2048 16384 28552 > g: 4194304 8675328 vinum 2048 16384 28552 > h: 2097152 12869632 vinum 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 > Filesystem Size Used Avail Capacity Mounted on > /dev/ad2s1a 135M 54M 70M 43% / > devfs 1.0K 1.0K 0B 100% /dev > /dev/vinum/home 90G 12K 83G 0% /home > /dev/vinum/tmp 4.3G 3.4M 3.9G 0% /tmp > /dev/vinum/usr 1.9G 954M 866M 52% /usr > /dev/vinum/usrports 1.9G 516M 1.3G 28% /usr/ports > /dev/vinum/usrlocal 1.9G 71M 1.7G 4% /usr/local > /dev/vinum/var 9.7G 1.0M 8.9G 0% /var > /dev/vinum/root 135M 54M 70M 44% /newroot You seem to have most things under Vinum as well, though it's not clear if they're related to the drive you've shown above. Remember the golden rule "only one drive per spindle". > 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? 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. --J/pvEKOcHgREgBce Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (FreeBSD) iD8DBQE/8l/IIubykFB6QiMRAqs9AJwNp3XO1jnsTlAYm1t4984qIcqmhwCdFWFs dN6anzkxo86ac6+JFNUOnVQ= =Sh6b -----END PGP SIGNATURE----- --J/pvEKOcHgREgBce--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031231053400.GO10758>