Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 63298 - out of space errors misrepresented
out of space errors misrepresented
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Adrian Likins
Jay Turner
Depends On:
Blocks: 61901 67218
  Show dependency treegraph
Reported: 2002-04-12 01:21 EDT by Chris Ricker
Modified: 2015-01-07 18:55 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-06-21 16:13:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chris Ricker 2002-04-12 01:21:30 EDT
I just tried to do a massive up2date.  The system was running beta4 (up2date
2.7.65-7.x.3), and I tried to up2date to all the new packages in the 7.2.93
channel.  The system had 400 megs free before the up2date (just a single /
partition for simplicity), and the update consisted of ~170 packages (roughly
200 megs of RPMs).

They downloaded successfully, but then none installed, failing because of disk
space.  However, if I manually upgrade them using rpm -Fvh in batches, they
upgrade just fine.

Furthermore, the error warning which popped up was ~170 lines long.  Instead of
using scroll bars, it generated a warning message ~170 lines long -- far, far
longer than the screen.  

I think this is different than #63056 (that sounds hardware, this sounds software)
Comment 1 Adrian Likins 2002-04-12 15:52:12 EDT
I assume the transaction failed if you tried to `rpm -Fvh ` all of
them at once? 

I definately see why it would out of space. 400 megs free on /,
200megs eaten by rpms, and then 200megs of rpms to get uncompressed
and exploded on the file system before the rpms themselves are deleted.

Part of the problem is that up2date does everything as one large
transaction set, and then deletes the installed rpms. Ideally,
it would figure out the big tranaction, split it into smaller ones
if possible, then for each smaller transaction, fetch the packages
needed, install them, deleted them, repeat for the rest of the
split out transactions. 

Thats not going to happen for the next release though. I'll
take a look at trying to make the space requirement detection
code more sophisticated in the mean time.
Comment 2 Chris Ricker 2002-04-12 22:20:06 EDT
I didn't actually try an -Fvh on the whole set.  I first manually upgraded rpm
(to minimize spurious .rpmnew droplets all over the system ;-) and all the
XFree86 rpms, and then did a -Fvh of everything else.  That worked....

Comment 3 Chris Ricker 2002-04-17 20:35:11 EDT
2.7.82-7 seems better, for the most part.  Now it just errors out.  Long-term,
something like poldok does (splitting up into transactions) would be better....

However, 2.7.82-7 does have very bizarre errors for out-of-space.  I'm now getting:

Test install failed because of package conflicts:
Installing package kernel-source-2.4.18-0.22 needs 7Mb on the / filesystem.

The test install *didn't* fail because of package conflicts.  It failed because
of space limitations....

Note You need to log in before you can comment on or make changes to this bug.