Red Hat Bugzilla – Bug 17884
infinite loop on non-sufficient disk space
Last modified: 2008-05-01 11:37:58 EDT
During an update of an existing RH 6.2 installation anacoda, in a text
mode, decides that is needs more space (fair enough if not nice) and
it goes into an infinite "prepare installation" loop without any
chance to intervene in other way but by a power switch.
What is more interesting that while it wanted an extra 251 MBytes
the first time subseqent requests are for 323 MB. This is probably
caused by an extra copy of an installtion image. I ended up with
on a root partition and another one in /usr.
Please repeat with the final 7.0 release to verify this is still a problem. I
think we handled this issue after RC2.
I am including this comment from the user (unable to connect to Bugzilla due to
This was with Beta CDs for Alpha. These CDs were made quite a bit later
than RC2. I have no idea if you transferred bug fixes from i386 to this
Repeating the problem could be a bit difficult. I had to reorganize
my disk to finish an installation and I do not have now RH 6.2 with
not enough space for an update. Also final 7.0 for Alpha does not
exist yet, AFAIK.
Sorry, I didn't catch this was on the Alpha - obviously you can't try the final
release out yet!
for the following scenario:
alpha miata minimum 6.2 install w/all disk space used (NO free space at all...)
upgrade to 7.0 using test tree 7.0-qa1017.0 fails with an rpm error right after
choosing to "Upgrade system" at the install type ... (rpm fails because there is
no space to upgrade the database) ...
__db_assert:0 failed: file "/../dist/../common/db_err.c", line 200
install exited abnormally -- received signal 6
and then the install dies ...
I think that you found another failure mode. Note that in my case there
was enough space to put one installation image on a root partition, and
another one after the first failure on /usr, but it turned out that there
is not enough space left for all packages to install (an update) and that
triggered a looping with a power switch as the only "exit condition".