Bug 33649
Summary: | Wolverine upgrade from 7.0 filled up /var and gave up without cleaning up | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | David D. Johnson <ddj> |
Component: | anaconda | Assignee: | Matt Wilson <msw> |
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-03-29 17:04:33 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
David D. Johnson
2001-03-28 18:30:53 UTC
These temporary files are removed if you exit the installer cleanly. Since you rebooted there was no opportunity to clean them up. Matt could we be better about looking in /var/lib/rpm and removing left over temp files to free space? Excuse me? Where does the installer give any option to exit cleanly when there is not enough space to do the upgrade? Before I rebooted, I went back and deselected some packages. Then when I clicked NEXT> to attempt the upgrade again, it created the second 14-meg copy of the database. THIS is where it should have cleaned up the temp space. For that matter, it should blow away any temp files it finds there before it begins the upgrade -- If I had booted the install CD again, I'll bet the garbage would have still been there. I checked in a patch to remove anaconda-rebuilddbXXXXXXXXX when a rebuild fails or when an upgrade package search fails. |