Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 104033 - Not possible to set LVM PE size in kickstart
Not possible to set LVM PE size in kickstart
Product: Red Hat Linux Beta
Classification: Retired
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2003-09-09 04:40 EDT by Jos Vos
Modified: 2007-04-18 12:57 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-01-16 12:16:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2003:344 normal SHIPPED_LIVE Miscellaneous bugfixes available for anaconda installation program 2003-11-11 00:00:00 EST

  None (edit)
Description Jos Vos 2003-09-09 04:40:57 EDT
Description of problem:
It is currently not possible to set the LVM PE size in Anaconda.  This is needed
if you (later) want to use > 256 GB LV's in the volume group that is created at
installation time.
Comment 1 Jos Vos 2003-09-09 04:50:46 EDT
Simple to add, it seems: in partRequests.py, class VolumeGroupRequestSpec's
__init__ already has a pesize parameter, so in defineVolumeGroup (kickstart.py)
a --pesize=<number> for defining the PE size has to be added and passed to the
call of partRequests.VolumeGroupRequestSpec.

(This is nearly a patch, isn't it... ;-))
Comment 2 Jeremy Katz 2003-09-23 11:06:20 EDT
Added in CVS
Comment 3 Jay Turner 2004-01-16 12:16:21 EST
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.