Why not resize your LVM before kickstarting? Seems to me it would be a lot easier to run a resize script on all the machines while they are up and running, THEN Kickstart them with the properly sized LVM's. -----Original Message----- From: kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Barry O'Rourke Sent: Friday, November 07, 2008 2:39 AM To: kickstart-list@xxxxxxxxxx Subject: Using kickstart to resize existing LVM partitions during a rebuild Hi, We have around 300 RHEL4 boxes that we are looking to upgrade to Scientific Linux 5, as part of the rebuild we would like to double the size of our current root partition to allow for future expansion and because they are getting a bit short on free space. Our current LVM set up looks like; /dev/mapper/ifp-slash 15Gb /dev/mapper/ifp-var 2Gb /dev/mapper/ifp-log 2Gb /dev/mapper/ifp-scratch fills the rest of the disk. We intend to script the shrinking of the ifp-scratch LV before starting the rebuild to free up 15Gb free space within the volume group which we would then like to add to the ifp-scratch LV during the rebuild. During the rebuild the ifp-scratch LV must stay intact as our users dump a lot of there data there. The problem that I've been having is that I can't figure out the syntax required for the logvol line in the kickstart file that will resize the ifp-slash to 30Gb. Every attempt that I've made so far seems to resize it to 15Gb as it was before. If you need any more information please let me know, and thanks in advance for any help that is offered. Barry _______________________________________________ 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
