* -re0212 * cd gui install In disk druid, (1) clear all partitions (2) create /boot (3) make two raid partitions (4) make a raid1 device, format as LVM (5) edit free space and format as LVM Traceback (most recent call last): File "/usr/lib/anaconda/iw/partition_gui.py", line 1030, in editCb self.editPartitionRequest(request, isNew = 1) File "/usr/lib/anaconda/iw/partition_gui.py", line 1087, in editPartitionRequest if self.refresh(): File "/usr/lib/anaconda/iw/partition_gui.py", line 1013, in refresh self.populate() File "/usr/lib/anaconda/iw/partition_gui.py", line 788, in populate self.tree[iter]['Size (MB)'] = "%g" % (request.getActualSize(self.partitions, self.diskset),) File "/usr/lib/anaconda/partRequests.py", line 604, in getActualSize partsize = req.getActualSize(partitions, diskset) File "/usr/lib/anaconda/partRequests.py", line 439, in getActualSize raise RuntimeError, "Checking the size of a partition which hasn't been allocated yet" RuntimeError: Checking the size of a partition which hasn't been allocated yet
Wasnt there also part of this that required the last partition being created to fail to be allocated due to the wierd cylinder roundoff error?
Probably, but I was getting that error by simply editing free space into a partition. It was only when I first set up lvm-on-raid and then edited free space into an LVM partition that I got the traceback to follow the "cylinder boundary" error dialog.
This is something I cannot reliable reproduce. If you have a particular machine/hard drive combination that will do this I can take a look. BTW the LVM and RAID stuff are a red herring as far as I can tell. Its more related to something in parted that gets confused about partition offsets and tells us there is a range of cylinders free and yet if you ask for that range it reports a problem.
Closing until we get a reliable reproducer.