Bug 82671 - anaconda does not detect lack of space on upgrades
anaconda does not detect lack of space on upgrades
Status: CLOSED WONTFIX
Product: Red Hat Public Beta
Classification: Retired
Component: rpm (Show other bugs)
phoebe
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
Mike McLean
:
Depends On:
Blocks: 79578
  Show dependency treegraph
 
Reported: 2003-01-24 14:05 EST by Mike McLean
Modified: 2007-04-18 12:50 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-01-25 12:41:09 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
test case (462 bytes, text/plain)
2003-01-24 16:44 EST, Jeremy Katz
no flags Details

  None (edit)
Description Mike McLean 2003-01-24 14:05:58 EST
* Phoebe public beta 2
* upgrade from 7.2 minimal

1) install 7.2 minimal, use a /boot partition
2) fill up all space in /boot
3) try to upgrade to Phoebe

The upgrade proceeds and begins installing packages, only to fail on the first
package that places files in /boot (redhat-logos in my case).  When it fails, it
gives me the "There was an error installing redhat-logos-...." dialog, which is
a fatal error.  

Don't we check to see if the packages will fit before we start installing them?
Comment 2 Jeremy Katz 2003-01-24 16:43:39 EST
I have this failing with a simple test case from the command line as well. 
Attached.
Comment 3 Jeremy Katz 2003-01-24 16:44:24 EST
Created attachment 89591 [details]
test case
Comment 4 Jeff Johnson 2003-01-25 12:41:09 EST
Both broken file systems and absolutely full systems
return exactly the same value in bavail, namely 0.

So the value 0 in bavail disables disk space accounting
in rpm.

WONTFIX, because it's silly and stupid to chase one exotic
value that hardly ever happens in practice, fails with adequate
strerror message that is perfectly sane and "obvious", and because
there will always be borked file systems that return bavail = 0,
and there's far too much borkage for me to run a file system black
list.
Comment 5 Mike McLean 2003-01-27 16:20:22 EST
Additional borkage:  filesystems with <5% free space (or whatever last bit is
reserved for root only by tune2fs) also exhibit this bug.

Confirmed that when the filesystem has 'regular' free space, the Disk Space
dialog is invoked.

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