Doing some quick googling of "logvol" AND "--grow" Gives me a couple examples where people are using just --grow on logvol definitions. Try making it the last argument in the definition string. logvol /opt/store/virtual_machines --vgname=vg_data --name=lv_virtual_machines --fstype=ext3 --size=1 --grow On 11/4/08 1:15 PM, "Thomas Callahan" <callahant@xxxxxxxxxx> wrote: > It looks like --grow requires an attribute, documentation shows "--grow=" > > Try --grow=max maybe? Or --grow=y > > I have not played with --grow on logvol yet. > > > > On 11/4/08 1:06 PM, "William J. Dennison" <william_dennison@xxxxxxx> wrote: > >> The Kickstart documentation located here >> (http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installation_Gui>> d >> e-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? > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/kickstart-list > _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list
