Hi, I stumbled upon an issue with the kickstart partitioning when trying to port our kickstart files from rhel4 to rhel5. For rhel4, the partitioning part of kickstart looked like
clearpart --all --initlabel part /boot --fstype ext3 --size=100 --asprimary part pv.01 --size 1 --grow --fstype "physical volume (LVM)" volgroup vg01 pv.01 logvol / --vgname=vg01 --fstype ext3 --size=15000 --name=rootLV logvol swap --vgname=vg01 --fstype swap --size=2560 --name=swapLV logvol /tmp --vgname=vg01 --fstype ext3 --size=5000 --name=tmpLV logvol /scratch --vgname=vg01 --fstype ext3 --size=1 --grow --name=scratchLV However, when trying to use this for kickstarting rhel5, it doesn't work. During the partitioning stage anaconda throws an exception "lvcreate failed for swapLV", and the installation is aborted. Swithing to another VT and looking at the LV:s that anaconda has created, it seems that the problem is that the scratchLV has been created before swapLV, and due to the --grow option it grows to fill all the space, without leaving enough space left for swapLV. Changing the kickstart file by setting a fixed size for scratchLV and removing --grow makes the the kickstart succeed, but having --grow work would be really convenient for our somewhat heterogeneous machines. OTOH, resizing /scratch online after the installation makes for a really cool demo of system-config-lvm. :) Am I missing something really obvious or is it time to enter an issue into bugzilla? Have other people seen something like this, at least on bugzilla I didn't find anything that looked relevant? -- Janne Blomqvist _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
