Red Hat Bugzilla – Bug 141370
anaconda doesn't specify pesize when writing anaconda-ks.cfg
Last modified: 2007-11-30 17:07:05 EST
Description of problem: writeKS in partitions.py does not specify the PE size of a volume group. When the user has specified a PE size greater than the default they may also specify larger LVs. However, if the anaconda-ks.cfg is actually used in this case, the creation of these LVs will fail because the PE size is prohibitively small (it will have defaulted to 4MB since the pesize was not specified). Version-Release number of selected component (if applicable): anaconda-9.1.3-3.RHEL How reproducible: Always Steps to Reproduce: 1. Install a system using LVM with pesize > 4MB and a logical volume of size > 256GB 2. Take the resulting /root/anaconda-ks.cfg and, after uncommenting the partitioning info, use it to kickstart another (or the same) system 3. Actual results: kickstart install fails because lvm specs say to create an LV > 256GB with a VG whose PE size is 4MB, which is not possible Expected results: kickstart works just like the install from whence it was generated Additional info:
Fixed in CVS for RHEL4 and HEAD
Mass-closing lots of old bugs which are in MODIFIED (and thus presumed to be fixed). If any of these are still a problem, please reopen or file a new bug against the release which they're occurring in so they can be properly tracked.