Bug 17884
Summary: | infinite loop on non-sufficient disk space | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Michal Jaegermann <michal> |
Component: | anaconda | Assignee: | Michael Fulbright <msf> |
Status: | CLOSED DEFERRED | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | alpha | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-10-17 22:24:47 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Michal Jaegermann
2000-09-26 21:38:53 UTC
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 network problems): 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 set. 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) ... fails with: __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". |