Bug 7882 - RPM incorrectly says there is no space on filesystem.
RPM incorrectly says there is no space on filesystem.
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
6.1
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Jeff Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-12-18 18:08 EST by richard.delorenzi
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:
Environment:
Last Closed: 1999-12-19 12:53:33 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)

  None (edit)
Description richard.delorenzi 1999-12-18 18:08:06 EST
Both GNORPM and kpackage give the following report when I try to install
star office (this package installed under 6.0), also tryed other packages.
I have All of RedHat6.1GPL installed. (this installed when I upgraded, I
did not use upgrade option I just overwrote the whole OS except /home then
fixed some config files in /etc)

Installing package XXXX needs 23M on / file system.

The root file system has 139M free.
df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/hda1             1.5G  1.3G  139M  90% /
/dev/hda5             499M  168M  305M  36% /home
/dev/hdb              411M  411M     0 100% /mnt/cdrom

It is read/write
mount
/dev/hda1 on / type ext2 (rw)
none on /proc type proc (rw)
/dev/hda5 on /home type ext2 (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/hdb on /mnt/cdrom type iso9660 (ro,nosuid,nodev,user=delor)
Comment 1 Jeff Johnson 1999-12-19 12:53:59 EST
Do you have symlinks pointing into /mnt/cdrom ?

Does the package have paths that traverse those symlinks?

Meanwhile, add --ignoresize to the rpm command to skip disk space checking.
Comment 2 Jeff Johnson 2001-01-08 14:24:00 EST
Closed for lack of input.

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