William J. Dennison wrote: > Already sent it there, seems someone on this list has responded to attempt to > help me, Thanks Joseph. BTW, The kickstart list seems very silent. >
It does seem to be decreasing in posts lately. That all being said, the archives remain an excellent resource. Maybe most of the questions have already been answered a few times -- that is probably a good sign :) This is a Google custom search engine that searches kickstart-list that may prove useful in the future: http://www.google.com/coop/cse?cx=016811804524159694721%3A1h7btspnxtu There are a lot of tricks and ideas there not in the main documentation. --Michael > Hi William, > > Here is an example of my ks.cfg partitioning using LVM and the --grow option: > > part /boot --fstype ext3 --size=100 --ondisk=\$d1 --asprimary > part pv.100000 --size \$pv1size --ondisk=\$d1 --asprimary > part pv.200000 --size > \$pv2size --grow --ondisk=\$d1 --asprimary > volgroup rootvg pv.100000 > volgroup datavg pv.200000 > logvol / --fstype > ext3 --vgname=rootvg --size=4192 --name=rootvol > logvol /tmp --fstype > ext3 --vgname=rootvg --size=548 --name=tmpvol > logvol /var --fstype > ext3 --vgname=rootvg --size=2048 --name=varvol > logvol swap --fstype > swap --vgname=rootvg --size=\$swapsize --name=swapvol > logvol /appdata --fstype > ext3 --vgname=datavg --size=1 --grow --name=appdatavol > > I had a similar issue and was because my VM had to small of a PV and I had > allocated all the space. But the grow option works just fine. > > If you can send the error (traceback) from anaconda I would be able to tell > you exactly what is wrong. > > Joseph Boyer Jr. > Liquidnet Holdings, Inc. > E [EMAIL PROTECTED] > T +1 646.660.8352 > C +1 646.284.8394 > > > On Tuesday 04 November 2008 03:06:08 pm Michael DeHaan wrote: > >> William J. Dennison wrote: >> >>> Some Data >>> >>> If I do BELOW IT WORKS >>> clearpart --all --initlabel >>> partition /boot --size=1000 --ondisk=sda --asprimary --fstype=ext3 >>> partition pv.01 --size=22000 --ondisk=sda --asprimary >>> partition pv.02 --size=1 --grow --ondisk=sda --asprimary >>> volgroup vg_system pv.01 >>> volgroup vg_data pv.02 >>> logvol / --vgname=vg_system --size=2000 --name=lv_root --fstype=ext3 >>> logvol /swap --vgname=vg_system --size=4000 --name=lv_swap --fstype=swap >>> logvol /usr --vgname=vg_system --size=4000 --name=lv_usr --fstype=ext3 >>> logvol /var --vgname=vg_system --size=2000 --name=lv_var --fstype=ext3 >>> logvol /var_log --vgname=vg_system --size=2000 --name=lv_var_log >>> --fstype=ext3 logvol /var_log_audit --vgname=vg_system --size=2000 >>> --name=lv_var_log_audit -- fstype=ext3 >>> logvol /var/tmp --vgname=vg_system --size=2000 --name=lv_var_tmp >>> --fstype=ext3 logvol /tmp --vgname=vg_system --size=2000 --name=lv_tmp >>> --fstype=ext3 logvol /opt --vgname=vg_system --size=1000 --name=lv_opt >>> --fstype=ext3 logvol /home >>> logvol /opt/store/virtual_machines --vgname=vg_data >>> --name=lv_virtual_machines --fstype=ext3 --size=1 --grow--vgname=vg_data >>> --size=10000 --name=lv_home --fstype=ext3 >>> >>> IF I ADD THE Following line above "/opt/ziplock/virtual_machines", it >>> croaks saying lvceate failed for lv_virtual_machines >>> lv_virtual_mlogvol /opt/store/incomming_data --vgname=vg_data --size=1000 >>> --name=lv_incom ming_data --fstype=ext3 >>> >>> On Tuesday 04 November 2008 01:48:57 pm Joseph Boyer Jr. wrote: >>> >>>> Hi William, >>>> >>>> Here is an example of my ks.cfg partitioning using LVM and the --grow >>>> option: >>>> >>>> part /boot --fstype ext3 --size=100 --ondisk=\$d1 >>>> --asprimary part pv.100000 --size \$pv1size --ondisk=\$d1 --asprimary >>>> part pv.200000 --size \$pv2size --grow --ondisk=\$d1 --asprimary >>>> volgroup rootvg pv.100000 >>>> volgroup datavg pv.200000 >>>> logvol / --fstype ext3 --vgname=rootvg --size=4192 >>>> --name=rootvol logvol /tmp --fstype ext3 --vgname=rootvg --size=548 >>>> --name=tmpvol logvol /var --fstype ext3 --vgname=rootvg --size=2048 >>>> --name=varvol logvol swap --fstype swap --vgname=rootvg >>>> --size=\$swapsize --name=swapvol logvol /appdata --fstype ext3 >>>> --vgname=datavg --size=1 --grow --name=appdatavol >>>> >>>> I had a similar issue and was because my VM had to small of a PV and I >>>> had allocated all the space. But the grow option works just fine. >>>> >>>> If you can send the error (traceback) from anaconda I would be able to >>>> tell you exactly what is wrong. >>>> >>>> Joseph Boyer Jr. >>>> Liquidnet Holdings, Inc. >>>> E [EMAIL PROTECTED] >>>> T +1 646.660.8352 >>>> C +1 646.284.8394 >>>> >>>> >>>> -----Original Message----- >>>> From: [EMAIL PROTECTED] >>>> [mailto:[EMAIL PROTECTED] On Behalf Of William J. >>>> Dennison Sent: Tuesday, November 04, 2008 1:06 PM >>>> To: cobbler mailing list >>>> Subject: Re: LOGVOL --grow Seems to Be Broken >>>> >>>> Thanks I will post there as well. >>>> >>>> On Tuesday 04 November 2008 12:42:30 pm Michael DeHaan wrote: >>>> >>>>> William J. Dennison wrote: >>>>> >>>>>> The Kickstart documentation located here >>>>>> (http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installat >>>>>> i on _Guide-en-US/s1-kickstart2-options.html) specifically notes that >>>>>> you can use "--grow" with a "logvol" parameter. When I do this the >>>>>> RHEL5 installation blows up. Is this an issue with Cobbler, Kickstart, >>>>>> RHEL 5 limitations, etc.? >>>>>> >>>>>> Below is my partitioning area in my kickstart file. >>>>>> >>>>>> ---------------------------------------------------------------------- >>>>>> - -- ------------------------------------------- clearpart --all >>>>>> --initlabel >>>>>> >>>>>> partition /boot --size=1000 --ondisk=sda --asprimary --fstype=ext3 >>>>>> >>>>>> partition pv.01 --size=22000 --ondisk=sda --asprimary >>>>>> partition pv.02 --size=1024 --grow --ondisk=sda --asprimary >>>>>> >>>>>> volgroup vg_system pv.01 >>>>>> volgroup vg_data pv.02 >>>>>> >>>>>> logvol / --vgname=vg_system --size=2000 --name=lv_root --fstype=ext3 >>>>>> logvol /swap --vgname=vg_system --size=4000 --name=lv_swap >>>>>> --fstype=swap logvol /usr --vgname=vg_system --size=4000 --name=lv_usr >>>>>> --fstype=ext3 logvol /var --vgname=vg_system --size=2000 --name=lv_var >>>>>> --fstype=ext3 logvol /var_log --vgname=vg_system --size=2000 >>>>>> --name=lv_var_log --fstype=ext3 logvol /var_log_audit >>>>>> --vgname=vg_system --size=2000 --name=lv_var_log_audit -- fstype=ext3 >>>>>> logvol /var/tmp --vgname=vg_system --size=2000 --name=lv_var_tmp >>>>>> --fstype=ext3 logvol /tmp --vgname=vg_system --size=2000 --name=lv_tmp >>>>>> --fstype=ext3 logvol /opt --vgname=vg_system --size=1000 --name=lv_opt >>>>>> --fstype=ext3 >>>>>> >>>>>> logvol /home --vgname=vg_data --size=10000 --name=lv_home >>>>>> --fstype=ext3 >>>>>> >>>>>> logvol /opt/store/incomming_data --vgname=vg_data --size=1000 >>>>>> --name=lv_incom ming_data --fstype=ext3 >>>>>> logvol /opt/store/saved_data --vgname=vg_data --size=1000 >>>>>> --name=lv_saved_data --fstype=ext3 logvol /opt/store/upload_data >>>>>> --vgname=vg_data --size=1000 --name=lv_upload_data --fstype=ext3 >>>>>> logvol /opt/store/export_data --vgname=vg_data --size=1000 >>>>>> --name=lv_export_data --fstype=ext3 logvol /opt/store/webserver >>>>>> --vgname=vg_data --size=1000 --name=lv_appserver --fstype=ext3 logvol >>>>>> /opt/store/dbserver >>>>>> --vgname=vg_data --size=1000 --name=lv_dbserver --fstype=ext3 logvol >>>>>> /opt/store/virtual_machines --vgname=vg_data --size=1 --grow >>>>>> --name=lv_virtual_machines --fstype=ext3 >>>>>> ---------------------------------------------------------------------- >>>>>> - -- >>>>>> ---------------------------------------------------------------------- >>>>>> - --- ------------- >>>>>> >>>>>> If I remove the --grow from "virtual_machines", all works fine, if I >>>>>> leave it in the Anaconda load blows up. When I run an interactive >>>>>> install, I notice that the --grow feature is not allowed on logvols. >>>>>> Does the logvol RED HAT documentation have to be edited? >>>>>> >>>>> It's not an issue with Cobbler, all Cobbler is doing is rendering your >>>>> kickstart file, and in this case, you've put in your own partitioning >>>>> logic manually (which is fine) >>>>> >>>>> Though someone might have your answer here, we have a whole mailing >>>>> list devoted to kickstart related questions, I'd suggest posting this >>>>> here instead: >>>>> >>>>> http://www.redhat.com/mailman/listinfo/kickstart-list >>>>> >>>>> --Michael >>>>> >>>>> >>>>> _______________________________________________ >>>>> cobbler mailing list >>>>> [email protected] >>>>> https://fedorahosted.org/mailman/listinfo/cobbler >>>>> >>>> -- >>>> William J. Dennison >>>> Principal Consultant >>>> SRA International Inc. - RABA Center >>>> 8830 Stanford Blvd, Suite 205 >>>> Columbia, Maryland 21045 >>>> Phone: (410) 715-9399 x2351 >>>> Mobile: (410) 218-5866 >>>> Email: [EMAIL PROTECTED] >>>> Email2: [EMAIL PROTECTED] >>>> Email3: [EMAIL PROTECTED] >>>> Jabber: [EMAIL PROTECTED] >>>> AIM: dennisonwjonly >>>> GTalk: [EMAIL PROTECTED] >>>> _______________________________________________ >>>> cobbler mailing list >>>> [email protected] >>>> https://fedorahosted.org/mailman/listinfo/cobbler >>>> >>>> >>>> _______________________________________________ >>>> cobbler mailing list >>>> [email protected] >>>> https://fedorahosted.org/mailman/listinfo/cobbler >>>> >> Kickstart-list :) >> >> *cough* >> >> --Michael >> >> _______________________________________________ >> cobbler mailing list >> [email protected] >> https://fedorahosted.org/mailman/listinfo/cobbler >> > > > > _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
