Bug 53216

Summary: up2date disk space computation not sophisticated enough
Product: [Retired] Red Hat Linux Reporter: Havoc Pennington <hp>
Component: up2dateAssignee: Adrian Likins <alikins>
Status: CLOSED DEFERRED QA Contact: Jay Turner <jturner>
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: aleksey, gafton, mihai.ibanescu, srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-08-06 22:15:28 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 Havoc Pennington 2001-09-05 05:45:16 UTC 
The total size of the selected packages (236646 kB) exceeds your free disk
space (79344 kB).
[root@dhcppc1 rhn]# df
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/hdc2               521780    415932     79344  84% /
/dev/hdc1               521748    190960    304284  39% /tmp
/dev/hdc6              6047724   3942416   1798100  69% /usr
none                    385540         0    385540   0% /dev/shm
/dev/hdc7              7085139   4362835   2363886  65% /home
/dev/hdc8              7362735   6233459    756772  90% /cvs
/dev/hda1              2047968   1716768    331200  84% /mnt/win

It's only looking at /, assuming all package data will go on that
partition. yeah my partitions are on crack. nonetheless. ;-)
Comment 1 Bill Nottingham 2001-09-05 13:36:23 UTC 
No. It downloads the packages to /var first. That's what the calculation is about.
Comment 2 Adrian Likins 2001-10-24 23:59:33 UTC 
*** Bug 53583 has been marked as a duplicate of this bug. ***
Comment 3 Aleksey Nogin 2001-11-03 21:25:58 UTC 
Note: bug 53583 is not an exact duplicate, it's about up2date not subtructing
already downloaded packages from free space requirements.

BTW, another case where up2date does not compute the free space correctly - when
kernel RPMs are being up2date'd up2date fails to leave enough space for initrd
creation! I had a situation (with Enigma) when up2date failed to account for
initrd and because of that didn't even have space to create grub.conf, so it
left the system with an empty grub.conf...