The Kickstart documentation located here (http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installation_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? -- 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: william_dennison@xxxxxxx Email2: wjdennison@xxxxxxxxx Email3: wjdennison@xxxxxxxxxxxxxx Jabber: wjdennison@xxxxxxxxxx AIM: dennisonwjonly GTalk: wjdennison@xxxxxxxxx _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list
