Bug 189022 - Upgrade doesn't tell you how much disc space you need
Upgrade doesn't tell you how much disc space you need
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
5
All Linux
medium Severity medium
: ---
: ---
Assigned To: Chris Lumens
Mike McLean
:
Depends On:
Blocks: FC6Target
  Show dependency treegraph
 
Reported: 2006-04-14 16:45 EDT by Nigel Horne
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-04-27 13:17:13 EDT
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 Nigel Horne 2006-04-14 16:45:25 EDT
Description of problem:
[ I've put this in redhat-config-packages because I couldn't find anywhere on
your system to note installation/upgrade problems ]

Version-Release number of selected component (if applicable):
Unknown

How reproducible:
Always

Steps to Reproduce:
1. Attempt to upgrade from FC4 to FC5
2.
3.
  
Actual results:
I am told I don't have enough disc space, but I am left guessing how much I need
to free. The dialog box should tell me how much is needed not just say that I
don't have enough. I now have to waste time deleting a bit, trying again,
deleting a bit, trying again and so on until I have removed enough.

Expected results:
'You need an extra xxx MB free disc space'

Additional info:

[root@mac id]# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/hda3              5866304   4709284    854220  85% /
/dev/hda5             13345680   4216092   9129588  32% /mnt/macos
Comment 1 Frank Arnold 2006-04-15 05:49:28 EDT
I guess you meant the installer, it's anaconda. Reassigning to it, and setting
arch to "All".

Does make much more sense, IMO. The total value could be included in
parenthesis, though.

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