[Server-devel] F11: re-installing on an LVM from Kickstart dies with 'name already in use'

David Lehman dlehman at redhat.com
Wed Oct 28 14:59:23 EDT 2009


On Wed, 2009-10-28 at 17:54 +0100, Martin Langhoff wrote:
> On Wed, Oct 28, 2009 at 3:39 PM, Martin Langhoff
> <martin.langhoff at gmail.com> wrote:
> > I am seeing anaconda die with a kickstart that defines LVMs and
> > partitions like this:

Probably clearpart no longer defaults to anything useful. To get the
behavior you want instead of relying on defaults you should use
'clearpart --linux' or 'clearpart --all'.

> >
> > 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?

It's hard to tell exactly what's going wrong without
seeing /tmp/storage.log. If you can file bugs, consider doing so.

Dave




More information about the Server-devel mailing list