Created attachment 339591 [details] vt3 screenshot Description of problem: Trying to do xen install into 10GB virtual disk. This has been working fine till now. Today I get: Could not allocate requested partitions: not enough free space on disks. kickstart part commands are: clearpart --linux part / --fstype ext3 --size=3000 --grow part swap --recommended bootloader --location=mbr
Created attachment 339592 [details] fdisk -l screenshot
Could you please attach /tmp/storage.log to this bug report? Thanks.
Created attachment 340073 [details] storage.log Looks like it's not recognizing the type of partition /dev/xvda1. May be in an indeterminate state from a previously aborted install.
Is this still a problem?
Well, I can still reproduce by copy the following: http://sw.cora.nwra.com/test/xenfdev64.bz2 into a xen disk image. This has the results of an aborted install which must have left the disk with partitions marked "Linux", but no recognizable filesystem in partition 1. Easy enough to zero out the xen disk image to work around though.
I'm not sure what the correct answer is here. What happens if you use clearpart --all? Or, can you not use that for some reason?
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Seeing this with today's rawhide. I can't use clearpart --all in general because I re-use some of these kickstart file for installs on dual-boot machines. I don't see why anaconda would not clear a partition marked "Linux" in the partition table and unknown contents with "clearpart --linux" set.
Created attachment 359688 [details] storage.log
Linux partitions are those with a "linux filesystem" on them. This includes things like ext3, ext4, etc. If you've got unknown contents on there, anaconda's going to ignore them. Do you know what's on xvda1? anaconda certainly can't figure it out.
But anaconda can recognize most "real" filesystems out there, right? And it know that it's not one of those either. I guess what irks me the most is that this system is in a state left from a failed anaconda install - where it labeled the partitions but never got to making the file systems. It seems like anaconda should be able to recover from that state.
*** Bug 519255 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
In F-11 and later "clearpart --linux" does not look at what the partition table entry type says (the 83 normally), but actually looks at what sort of filesystem is on the partition as the partition table entry type is not a very reliable indicator of what a partition is actually used for. So if you have a hosed partition you want to reuse, you need to use "clearpart --all", or manually remove the partition from the table before installing.