RE: Vinum on Root
I went back to the original root install method as per the book, and I got vinum working. Now, needed to change the size of the var volume, since during install I followed the book example and had var take up the rest of the disk, in my case all 187Gigs of it :). Was under the impression that it would be easy to resize or at least remove and create a new smaller var once the base is working. So, backed up the /var directory. Started the vinum prompt and used rm to remove the var subdisk, then remove the var plex and finally was able to remove the var volume. Now ran create vinum_var.conf - in this case the file was simply: volume var plex org concat sd len 1g drive rootdev So, did not use the offset, since vinum is now working and should know where the next 1g should come from. Is this a bad assumption? Well, the vinum create worked fine. Then copied the backed up /var contents to the new vinum volume. Did a reboot, and reboot failed. System requesting to run fsck. So, in single user mode did this and got the following error: "** /dev/vinum/var (NO WRITE) CANNOT READ BLK: 381244736 CONTINUE? Yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 381244736, 381244737, 381244738, 381244739, /dev/vinum/var: CANNOT FIGURE OUT FILE SYSTEM PARTITION So, what should I have done and is there a way to back out of this? By the way, it a great book, I'm just a little thick when it comes to vinum & new unix. So, know I'm trying to do a lot right out of the gate - so really appreciate all the help I've been getting from everybody! Thanks again, Richard > >>> I. 1. setup unix partitions for swap, /, /usr, and /var > >>> 2. install FreeBSD5.1 > >>> 3. go through the bsdlabel -e > >>> 3.1 modify the swap with the 281 offset > >>> 3.2 add vinum partition h: with the same size as c:, but with > >>> a 16 offset > >>> 4. create a vinum config file > >>> --> 4.1 map each sub-disk to the exact size and offset as the > >>> unix partitions > >>> II.1. setup unix partitions for swap and / > >>> 2. install FreeBSD5.1 > >>> 3. go through the bsdlabel -e > >>> 3.1 modify the swap with the 281 offset > >>> 3.2 add vinum partition h: with the same size as c:, but with > >>> a 16 offset > >>> 4. create a vinum config file > >>> --> 4.1 create sub-disks using simply the size you want with no > >>> offset > > So, if I use Method I, as you specified in the book, can I then move > those > > particular partitions (/, /usr, /var) around without worrying about the > > original unix partition layout (offsets etc)? So, the original /, /usr, > /var > > sizes and offsets won't limit the location of the /dev/vinum/root, > > /dev/vinum/usr, /dev/vinum/var? > > They will for root, because you boot from the partition, not the > volume. Also, you should understand that moving partitions means > moving data. > > > For the mirroring case, should the swap partitions be mirrored too? > > That depends on whether you want to still have a swap partition if a > drive fails :-) > > 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: Vinum on Root
Sorry, my bad - needed to do newfs. Once I did this the fsck worked perfectly. Thanks again for all the help. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Vinum on Root
[Format recovered--see http://www.lemis.com/email/email-format.html] I wish you'd get a functional MUA. On Tuesday, 29 July 2003 at 23:29:46 -0700, Richard Johannesson wrote: > I went back to the original root install method as per the book, and I got > vinum working. > > Now, needed to change the size of the var volume, since during install I > followed the book example and had var take up the rest of the disk, in my > case all 187Gigs of it :). Was under the impression that it would be easy to > resize or at least remove and create a new smaller var once the base is > working. > > So, backed up the /var directory. Started the vinum prompt and used rm to > remove the var subdisk, then remove the var plex and finally was able to > remove the var volume. Now ran create vinum_var.conf - in this case the file > was simply: >volume var > plex org concat >sd len 1g drive rootdev > So, did not use the offset, since vinum is now working and should know where > the next 1g should come from. Is this a bad assumption? No, that's the way it should work. > Well, the vinum create worked fine. Then copied the backed up /var > contents to the new vinum volume. Did a reboot, and reboot > failed. System requesting to run fsck. So, in single user mode did > this and got the following error: "** /dev/vinum/var (NO WRITE) > > CANNOT READ BLK: 381244736 > CONTINUE? Yes > > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 381244736, 381244737, > 381244738, 381244739, > /dev/vinum/var: CANNOT FIGURE OUT FILE SYSTEM PARTITION > > So, what should I have done and is there a way to back out of this? It's difficult to say. I'd guess that you've done something wrong that you haven't reported (and probably haven't noticed). Both the man page and http://www.vinumvm.org/vinum/how-to-debug.html give you a list of information to supply if you have problems. Got through that and you may find the problem by yourself. Otherwise report here and I'll see what I can do. 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: Vinum on Root
[Format recovered--see http://www.lemis.com/email/email-format.html] Mutilated quotation, known broken MUA: > X-Mailer: Microsoft Outlook, Build 10.0.4510 On Tuesday, 29 July 2003 at 18:54:53 -0700, Richard Johannesson wrote: > On Tuesday, July 29, 2003 6:25 PM, Greg 'groggy' Lehey wrote: >> On Tuesday, 29 July 2003 at 18:00:25 -0700, Richard Johannesson wrote: >>> What I trying to get to is that there seems to be two styles of getting >>> vinum setup on a root drive: >>> I. 1. setup unix partitions for swap, /, /usr, and /var >>>2. install FreeBSD5.1 >> >> It doesn't have to be 5.1. > > Ok, good to know. > >>>3. go through the bsdlabel -e >>>3.1 modify the swap with the 281 offset >>>3.2 add vinum partition h: with the same size as c:, but with a >>> 16 offset >>>4. create a vinum config file >>> -->4.1 map each sub-disk to the exact size and offset as the unix >>> partitions >>> >>> II.1. setup unix partitions for swap and / >>>2. install FreeBSD5.1 >>>3. go through the bsdlabel -e >>>3.1 modify the swap with the 281 offset >>>3.2 add vinum partition h: with the same size as c:, but with a >>> 16 offset >>>4. create a vinum config file >>> -->4.1 create sub-disks using simply the size you want with no >>> offset >>> >>> Method I. comes from the Complete FreeBSD book. I actually got >>> this to work, but was wondering about the inflexibility of not >>> being able to change the partition sizes very easily. >> >> Once you have Vinum up and running, you can add and remove plexes and >> move things around like that. > > So, if I use Method I, as you specified in the book, can I then move those > particular partitions (/, /usr, /var) around without worrying about the > original unix partition layout (offsets etc)? So, the original /, /usr, /var > sizes and offsets won't limit the location of the /dev/vinum/root, > /dev/vinum/usr, /dev/vinum/var? They will for root, because you boot from the partition, not the volume. Also, you should understand that moving partitions means moving data. > For the mirroring case, should the swap partitions be mirrored too? That depends on whether you want to still have a swap partition if a drive fails :-) 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: Vinum on Root
> -Original Message- > From: [EMAIL PROTECTED] [mailto:owner-freebsd- > [EMAIL PROTECTED] On Behalf Of Greg 'groggy' Lehey > Sent: Tuesday, July 29, 2003 6:25 PM > To: Richard Johannesson > Cc: [EMAIL PROTECTED] > Subject: Re: Vinum on Root > > On Tuesday, 29 July 2003 at 18:00:25 -0700, Richard Johannesson wrote: > > Is it possible to create vinum on a root drive without using the offsets > in > > the vinum configuration file? > > You need a configuration file to set up Vinum. If you mean "Is it > possible to create vinum on a root drive without specifying offsets in > the vinum configuration file?", the answer is yes. Sorry that's what I meant. Ok, that's good to hear. > > What I trying to get to is that there seems to be two styles of getting > > vinum setup on a root drive: > > I. 1. setup unix partitions for swap, /, /usr, and /var > >2. install FreeBSD5.1 > > It doesn't have to be 5.1. Ok, good to know. > >3. go through the bsdlabel -e > >3.1 modify the swap with the 281 offset > >3.2 add vinum partition h: with the same size as c:, but with a > > 16 offset > >4. create a vinum config file > > -->4.1 map each sub-disk to the exact size and offset as the unix > > partitions > > > > II.1. setup unix partitions for swap and / > >2. install FreeBSD5.1 > >3. go through the bsdlabel -e > >3.1 modify the swap with the 281 offset > >3.2 add vinum partition h: with the same size as c:, but with a > > 16 offset > >4. create a vinum config file > > -->4.1 create sub-disks using simply the size you want with no > > offset > > > > Method I. comes from the Complete FreeBSD book. I actually got this to > work, > > but was wondering about the inflexibility of not being able to change > the > > partition sizes very easily. > > Once you have Vinum up and running, you can add and remove plexes and > move things around like that. So, if I use Method I, as you specified in the book, can I then move those particular partitions (/, /usr, /var) around without worrying about the original unix partition layout (offsets etc)? So, the original /, /usr, /var sizes and offsets won't limit the location of the /dev/vinum/root, /dev/vinum/usr, /dev/vinum/var? > > Method II. Can't get this to work yet, but if it can work then should be > > superior given the flexibility that is gained. > > That'll work, but then you need to populate the volumes. > > > So, can Method II work on a root drive? > > Sure. > > > If Method II works, why would you then ever want to implement Method > > I? > > It's easier. You don't have to find a way to put things in your new > volumes. Ok, Method I is the best way to bootstrap the whole process, and once you have a base setup running on vinum you still have the flexibility of Method II anyway. If that's right, then Method I is definitely the way to go. > Greg For the mirroring case, should the swap partitions be mirrored too? Was under the impression that swap might be handled by a completely separate process and that there was no need for vinum to have to handle any swap stuff. Thanks again, Richard > -- > 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: Vinum on Root
On Tuesday, 29 July 2003 at 18:00:25 -0700, Richard Johannesson wrote: > Is it possible to create vinum on a root drive without using the offsets in > the vinum configuration file? You need a configuration file to set up Vinum. If you mean "Is it possible to create vinum on a root drive without specifying offsets in the vinum configuration file?", the answer is yes. > What I trying to get to is that there seems to be two styles of getting > vinum setup on a root drive: > I. 1. setup unix partitions for swap, /, /usr, and /var > 2. install FreeBSD5.1 It doesn't have to be 5.1. > 3. go through the bsdlabel -e > 3.1 modify the swap with the 281 offset > 3.2 add vinum partition h: with the same size as c:, but with a > 16 offset > 4. create a vinum config file > --> 4.1 map each sub-disk to the exact size and offset as the unix > partitions > > II.1. setup unix partitions for swap and / > 2. install FreeBSD5.1 > 3. go through the bsdlabel -e > 3.1 modify the swap with the 281 offset > 3.2 add vinum partition h: with the same size as c:, but with a > 16 offset > 4. create a vinum config file > --> 4.1 create sub-disks using simply the size you want with no > offset > > Method I. comes from the Complete FreeBSD book. I actually got this to work, > but was wondering about the inflexibility of not being able to change the > partition sizes very easily. Once you have Vinum up and running, you can add and remove plexes and move things around like that. > Method II. Can't get this to work yet, but if it can work then should be > superior given the flexibility that is gained. That'll work, but then you need to populate the volumes. > So, can Method II work on a root drive? Sure. > If Method II works, why would you then ever want to implement Method > I? It's easier. You don't have to find a way to put things in your new volumes. 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
