Bug 17655 - Disk Druid limts root / partition to 500Mbytes
Summary: Disk Druid limts root / partition to 500Mbytes
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 7.3
Hardware: alpha
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-09-18 19:00 UTC by harry.heinisch
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-10-18 13:26:08 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description harry.heinisch 2000-09-18 19:00:27 UTC 
When creating 2 partitions, root "/" and swap, it appears that Disk Druid 
will not allow you to set root to the whole disk.It limits you to 
500MBytes, forcing the user to add another partition /usr which can be set 
to use the whole disk.

Norberto
Comment 1 harry.heinisch 2000-09-18 19:08:59 UTC 
Same problem found on Red Hat 6.2

Norberto
Comment 2 Nalin Dahyabhai 2000-09-18 20:42:36 UTC 
Disk Druid is part of the installer, anaconda.  Reassigning to the "anaconda"
component.
Comment 3 Michael Fulbright 2000-09-19 21:59:38 UTC 
What is the geometry of the disk in question?

Whatever partition that /boot resides on can only occupy up to the 1024 limit
imposed by LILO.
Comment 4 Gene Czarcinski 2000-09-20 20:37:53 UTC 
I successfully created and installed beta4 in a 2GB and (separately) a 3GB
system.  The disks are 9GB scsi.

Gene
Comment 5 Brock Organ 2000-10-17 21:16:25 UTC 
are you still seeing this problem with the recent alpha release candidate ...?
we have not seen this issue in our internal testing ... :(
Comment 6 Brock Organ 2000-10-18 13:26:05 UTC 
please reopen if this is still a problem with the latest alpha release candidate
...
Note You need to log in before you can comment on or make changes to this bug.