Red Hat Bugzilla – Bug 12106
installer hangs if not enough space available
Last modified: 2008-05-01 11:37:56 EDT
I only had 1 gig in /usr, and told it to install everything. It popped up
a dialog box that I didn't have enough space, and then hung.
The installer just does not deal with space problems as gracefully or accurately
as it should.
For beta 2 install, I made a 1700 M /usr partition. I selected everything under
custom install (1496 M). The installer told me I needed 150 M more free (which
shouldn't be true), and then hung.
verified ... thanks for the report!
Also see #12292. Similar (but sufficiently different not to close as a
*** Bug 12292 has been marked as a duplicate of this bug. ***
I marked 12292 as a duplicate of this even though the two bugs are slightly
different, when the installer handles insufficient space conditions better, both
issues should be resolved ...
*** Bug 12281 has been marked as a duplicate of this bug. ***
*** Bug 12344 has been marked as a duplicate of this bug. ***
*** Bug 12392 has been marked as a duplicate of this bug. ***
This defect is considered MUST-FIX for Winston Beta-5
Does this happen in beta3?
Hi - yes BETA3 is still afflicted. I never finished installing BETA3 due to this
The bug gives the impression that the install hangs immediately after the "out
of space message". Maybe that happens for some people, but my experience has
always been this
1) "Out of space" message is shown.
2) I get an error box about being unable to unmount some partition. Usually
3) The installer happily lets me use "Back" to go back to package selection and
deselect a few packages
4) Upon going forward again from package selection, the hang occurs when the
installer checks for sufficient space the second time. As far as I remember the
"transferring install image" works OK, and the hang occurs immediately after the
"preparing to install" stage.
5) After the hang, the text console shows a python traceback which is
complaining about being unable to mount a partition because it is already
Hope this helps!
*** This bug has been marked as a duplicate of 10855 ***