Red Hat Bugzilla – Bug 66509
anaconda leaves junk in /var/lib on failed upgrade
Last modified: 2007-04-18 12:43:06 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.2.19-6.2.16-KRUD-perfctr2.3.6
Description of problem:
If an upgrade install (for example, 7.2==>7.3) fails because of
fatal error (media, disk space, EPERM in rpm), then anaconda
leaves a junk directory /var/lib/anaconda-rebuilddbNNNNNNNNNN
which can contain 25MB or more of space. Either this directory
should be removed automatically, or anaconda should give a
message about it. [If an upgrade fails once, then chances are
it will fail a couple more times before succeeding, and
losing 25MB of disk space each time can cause a failure itself!]
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. /usr/bin/chattr +i /bin/cp # make immutable some file that will be upgraded
2. Attempt to upgrade; it will fail due to EPERM in rpm
3. Reboot, and look in /var/lib/anaconda*
Actual Results: $ du -s /var/lib/anaconda*
Expected Results: Either: no junk in /var/lib; or, a message about it.
Assigning to an engineer.
We don't do rebuilds in the general case anymore, so this isn't a problem with
our current codebase.