Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: If an installation of F12 is attempted and there's not enough disk space, anaconda just crashes with a traceback, instead of giving a proper error message (as earlier versions did). This occurs just before the package installation screen (showing package name, version, description, and progress bar) should appear. Version-Release number of selected component (if applicable): anaconda-12.32-1.fc12 anaconda-12.30-1.fc12 (perhaps others) How reproducible: Doesn't always crash/traceback; sometimes it just hangs. Steps to Reproduce: This occurred with a kickstart installation into separate /, /usr, and /var partitions (also /tmp on tmpfs), with 2481 packages. /usr was approx. 6.8 GiB (which anaconda 12.17 reported as being 54 MiB too small). Installation was booted from a boot.iso image on DVD, using a repo in an ISO image on local hard disk (also containing images/install.img, as anaconda insists upon), with the kickstart cfg file on USB flash drive. (This was actually on a VMware virtual machine; stick the word "virtual" in front of each hardware description.) Actual results: anaconda crashes with a traceback ("this is probably a bug"), or just hangs. Expected results: A popup window as before, detailing the reason for the disk space shortage. Additional info: anaconda 12.17 gives a proper error popup (the source of the report of the 54 MiB shortage). BTW, the space required in /usr apparently includes a lot of overhead; the finished /usr uses 5.8 GiB, whereas anaconda reported that 6.8 GiB was 54 MiB too small.
If you are not getting a full error message, can you please switch to tty1 and see if there's an additional traceback being displayed there? Sometimes if there's a bug with the exception handling stuff, it looks like nothing's happening because we have no way of handling that secondary traceback. You can also see if there's a /tmp/anaconda-tb-*, /tmp/anaconda.log, and /tmp/storage.log and attach them to this bug report if they exist. Thanks.
Created attachment 367235 [details] Anaconda traceback (including storage.log) I also see this problem. Using Fedora 12 Beta, I have a laptop with HDD fully occupied by Vista - no free space. To reproduce: choose defaults all the way through until the partitioning configuration screen. At that point I (for example) choose shrink existing partition, and check "Review and modify partitioning layout". In the next screen, click New to add a new partition. Enter any old mount point, e.g. /foo and click OK. Since there's no free space, anaconda pops up a box titled "Error Partitioning": "Could not allocate requested partitions: not enough free space on disks." which is as expected. But click on OK and a new box pops uptitled "Add Partition": "An unhandled exception has occured. This is most likely a bug. Please save a copy of the detailed exception and file a bug report." And that is what I am attaching. FAOD the F12 Beta contains anaconda 12.37. If this always happens any time a user tries to make a partition larger than available space, then I think the priority may want to be increased as that seems like something which users could often do.
Bruce - is the traceback in comment #2 the same as the one you were getting? It seems unlikely to me.
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
Does this bug still persists in current rawhide? --- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
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.