Bug 11339 - Installer checks for space on /usr but doesn't on /
Installer checks for space on /usr but doesn't on /
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Erik Troan
Depends On:
  Show dependency treegraph
Reported: 2000-05-09 16:58 EDT by Mark Neidorff
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-05-12 11:55:07 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 Mark Neidorff 2000-05-09 16:58:22 EDT
I've upgraded from 5.2 to 6.2 and run into a problem.  When I started the
upgrade, the installer checked and told me that I didn't have enough free
space on the /usr partition, so I cleared some room and restarted the
install.  This is my partition table:

sda1     /         100Mb
sda2     /home     100Mb
sda3     swap      100Mb
sda4 <extended>
sda5    /usr       1,000Mb
sda6    /usr/src     500Mb
sda7    /usr/local 1,000Mb

The installer told me that it completed successfully. When I tried to start
an X session, I was told that there was no room on /tmp.  I checked and
found that the / partition was filled.  The bug I'm reporting is that it
appears that the installer is supposed to check for available disk space,
but it is not doing so completely.  Also, do I have any options for getting
my system back in working order, short of repartitioning and reinstalling?

Thank you,

Mark Neidorff
Comment 1 Erik Troan 2000-05-12 11:55:59 EDT
If the install didn't complain about being out of disk space, the packages
made it on there -- it does not leave any free space around necessarily. I
suspect you went into root's reserved space (which the installer can use, but
normal users cannot).

I'd thin kabout moving /tmp somewhere a bit bigger.

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