The following was filed automatically by anaconda: anaconda 11.5.0.59 exception report Traceback (most recent call first): File "/tmp/updates/storage/devices.py", line 2048, in _setSize raise ValueError("not enough free space in volume group") File "/tmp/updates/storage/partitioning.py", line 1163, in growLVM lv.size += grow_amounts[lv.name] File "/tmp/updates/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
Created attachment 358797 [details] Attached traceback automatically from anaconda.
My partition were also empty ... but it was after a first fail attempt with Bug 491754 - DeviceError: cannot commit to disk sda after 5 attempts
Just remembered that there was only one empty space ( 299 mb ) and the others were formatted ( by the previous failed installation ), but also empty. So it should just come back to the previous screen if there was not enough empty space with a warning message, instead of failing [ ... ]
Is this improved in F12 Alpha? There's been a fair number of partitioning fixes since F11 came out, some specifically for these issues you're seeing right now.
Maybe I should try the new Alpha release to confirm.
Just tried the Alpha release and have the same Bug 491754 - DeviceError: cannot commit to disk sda after 5 attempts ... but that's not part of this current bug anyway.
Created attachment 363353 [details] anaconda traceback Exception is still raising with current i386 rawhide, it occured when 'Use free space' choice was used (not necessarily with 'Review' checked). Reported information is correct, there is most probably no free space (all available space is allocated in partitions, lvs, md raid members, filesystems, ...), just the report shouldn't be so ultimate. ;)
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
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.