Description of problem:
After modifying a kickstart file to create LVM PV's, VG's, and LV's, I received
an error in anaconda ("Logical volume size must be larger than the volume
group's physical extent size.").  I used a partition setup that works
successfully on FC5:

part /boot --asprimary --fstype=ext3 --size=96 --ondisk=sda
part pv.01 --asprimary --size=512 --grow --ondisk=sda
volgroup vg.01 pv.01
logvol swap --fstype=swap --size=512 --vgname=vg.01 --name=swap
logvol / --fstype=ext3 --grow --size=1 --vgname=vg.01 --name=root

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

How reproducible:
Always

Steps to Reproduce:
1. Generate a kickstart file (used system-config-kickstart-2.6.13-1)
2. Manually change partitioning using a setup that worked in FC5
3. Start a kickstart install

Actual results:
Receive the "Logical volume size must be larger than the volume group's physical
extent size." error.

Expected results:
Successful partitioning and kickstart installation continues.

Additional info:
The problem appears to be that the "--grow" option is not considered when the
sanity checks are performed.  After checking the anaconda source, I found the
error message on line 924 of partRequests.py.  The logic in that particular test
checks that the supplied size (*1024) is not less than the default LVM PE size
(32768).  I had followed the basic output of system-config-kickstart, which sets
"--size=1" when the "--grow" option is used.  Once I saw the logic in the test
that was failing, I changed to "--size=512" (along with the "--grow" option) in
the kickstart file, and the installation proceeded as expected.