Bug 49192 - Autopartitioning not creating large enough partitions
Autopartitioning not creating large enough partitions
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Brent Fox
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2001-07-16 15:14 EDT by Bryan Leopard
Modified: 2007-04-18 12:34 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-16 10:47:57 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 Bryan Leopard 2001-07-16 15:14:56 EDT
PL ML350 1Ghz
1x9Gb hard drive

select server install - x-windows and Gnome
select autopartition - remove all linux partitions - ok
formats partitions ok
starts to load files - and quits with an error:

"you don't appear to have enough disk space
to install the packages you seleted. You
need more space on the following filesystems:
mount point /usr space needed 457M"
Comment 1 Michael Fulbright 2001-07-17 11:51:20 EDT
This issue is most likely because we were not rereading the partition table
correctly. We have addressed this bug in beta 2 - please retry and let us know
the outcome.
Comment 2 Glen Foster 2001-07-17 14:56:10 EDT
This defect considered MUST-FIX for Fairfax gold-release.
Comment 3 Brent Fox 2001-07-24 17:15:16 EDT
Please reopen if this bug is not fixed in Beta 2.
Comment 4 Bryan Leopard 2001-07-30 15:28:18 EDT
still fails with not enough room in Beta 2
Comment 5 Jeremy Katz 2001-07-30 19:02:29 EDT
Is there still not enough space with beta3?
Comment 6 Brent Fox 2001-08-13 23:16:41 EDT
bryan, any more info here?
Comment 7 Bryan Leopard 2001-08-15 09:26:13 EDT
I am trying to get the information from my engineer.
Comment 8 Brent Fox 2001-08-16 10:47:53 EDT
Comment 9 Bryan Leopard 2001-08-21 16:09:03 EDT
This is fixed in RC1.

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