Bug 206039

Description of problem:
When doing kickstart installation, I'm getting error that "logical volume must
be larger than physical extent size".  The part of kickstart script that defines
partitions looks like this:

clearpart --initlabel --drives=sda
part /boot --size 256 --ondisk sda --asprimary
part pv.00 --size 1 --grow --ondisk sda --asprimary
volgroup sys pv.00
logvol / --name root --vgname sys --fstype ext3 --size 1000
logvol swap --name swap --vgname sys --fstype swap --size 256
logvol /tmp --name tmp --vgname sys --fstype ext3 --size 64
logvol /var --name var --vgname sys --fstype ext3 --size 1000
logvol /srv --name srv --vgname sys --fstype ext3 --size 1 --grow

This above lines used to work just fine in RHEL4 and FC5.  The disk in question
is 4GB disk (virtual disk in vmware).

If I let Anaconda to autopartition the disk (using autopart instead of the above
lines), I can see it created physical volume with 32MB extent size.  So even my
smallest partition (/tmp) should be OK there.  Unless Anaconda is using
different default extent size for autoparitioning and for manual partitioning. 
I'm not aware of any kickstart option to force differnt extent size when
creating physical volume.

I also attempted chaning /tmp to 256MB, and got same error message.

BTW, any special reason for using big extent sizes (32MB) when creating physical
volumes in Anaconda?

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: