Red Hat Bugzilla – Bug 185186
Pup (Yum?) doesn't handle disk full situation.
Last modified: 2007-11-30 17:11:27 EST
Description of problem:
When upgrading a machine with limited disk space, if pup (or actually yum)
manages to download all the required packages, pup does not handle disk-full
errors during the package installation itself, nor does it report that any error
Once pup finished updating the machine it just closed down (crashed?).
Thinking the installation succeeded, I proceeded to reboot the machine but the
the reboot attempt failed.
Booting into CD rescue mode, I determined that the main root disk was full and
that yum failed to install the 2038 kernel initrd image leaving the machine in
Sadly enough, due to reasons beyond my control I was forced to delete the master
FC5T3 vmware image so I cannot reproduce the problem. (Getting a meaningful
error code out of yum/pup)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install FC5T3
2. Use pup/yum to determine how much space is required to download the latest
3. Full the root partition to "<root size> - <yum download size + 30MB>"
4. Fire up pup, let it update all the packages.
1. Pup downloads the packages.
2. Pup install the packages.
3. Pup closes. No error code.
1. Pup should warn user that there's insufficient space to install required
2. If user insist on installing the updates and yum/rpm fails due to
insufficient disk space, display a meaningful error code.
3. Role back changes?
Can you look in the xsession errors to see if there's anything there? most
things like this are at least trying to be caught, although there could be
something being missed
Umm... Sadly enough, I need to reinstall the machine so I can't really reproduce
This is yum -- Seth is working on adding checking into yum itself at which
point, pirut can catch the error and display it usefully for the user.
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer
test releases. We're cleaning up the bug database and making sure important bug
reports filed against these test releases don't get lost. It would be helpful if
you could test this issue with a released version of Fedora or with the latest
development / test release. Thanks for your help and for your patience.
[This is a bulk message for all open FC5/FC6 test release bugs. I'm adding
myself to the CC list for each bug, so I'll see any comments you make after this
and do my best to make sure every issue gets proper attention.]
This should be handled a lot better in Fedora 7 and later