On Wed, Oct 28, 2009 at 3:39 PM, Martin Langhoff
<martin.langhoff@xxxxxxxxx> wrote:
> I am seeing anaconda die with a kickstart that defines LVMs and
> partitions like this:
>
> clearpart --drives=sda
> bootloader --location=mbr
> part /boot --fstype ext3 --size=100 --ondisk=sda
> part / --fstype ext3 --size=2048 --maxsize=8192 --grow --ondisk=sda
> part pv.6 --size=1025 --grow --ondisk=sda
> volgroup VolGroup00 --pesize=32768 pv.6
> logvol /library --fstype ext3 --name=LogVol00 --vgname=VolGroup00
> --size=1 --grow
> logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00
> --size=1024 --maxsize=2048 --grow
The same definition dies on a blank disk -- with the following backtrace
anaconda 11.5.0.59 exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/storage/devices.py", line 2048, in _setSize
raise ValueError("not enough free space in volume group")
File "/usr/lib/anaconda/storage/partitioning.py", line 1163, in growLVM
lv.size += grow_amounts[lv.name]
File "/usr/lib/anaconda/storage/partitioning.py", line 197, in doAutoPartition
growLVM(anaconda.id.storage)
File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep
rc = stepFunc(self.anaconda)
File "/usr/lib/anaconda/dispatch.py", line 128, in gotoNext
self.moveStep()
File "/usr/lib/anaconda/gui.py", line 1339, in nextClicked
self.anaconda.dispatch.gotoNext()
ValueError: not enough free space in volume group
Is the LV definition invalid for some reason? Is LV expected to work?
cheers,
m
--
martin.langhoff@xxxxxxxxx
martin@xxxxxxxxxx -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
Attachment:
anaconda.log.gz
Description: GNU Zip compressed data
Attachment:
anacdump.txt.gz
Description: GNU Zip compressed data
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
