Bug 49428 - Disk Druid mount definition fails with 3 partitions
Summary: Disk Druid mount definition fails with 3 partitions
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 7.3
Hardware: i386 Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2001-07-19 15:08 UTC by Richard Forrister
Modified: 2007-04-18 16:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-07-20 14:22:20 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Richard Forrister 2001-07-19 15:08:00 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; SunOS 5.7 sun4u)

Description of problem:
If you use fdisk to partition your drive and create > 4 partitions, the
mount naming step in disk druid that follows will not recognize any
partitions other than 1 and 5.  All other partitions have type "None" and
no mount point can be specified.  Attempting to edit the partition in disk
druid at that point fails.

How reproducible:

Steps to Reproduce:
1.Select fdisk for disk partitioning.
2.Create /dev/hda1,primary; hda2, primary; hda3,extended; hda4, primary. 
Then create hda5,6,7,8
3.Save partition data, select Next.
4.In Disk Druid partition /dev/hda1 will be shown as type Ext3 and it's
mount point can be specified.  /dev/hda5 will be shown as type Ext2, and
it's mount point can be specified.  All other partitions will be shown as
type "None" and no mount points can be specified.	

Actual Results:  See steps to reproduce above.

Expected Results:  Partitions should have been shown as Ext2, 3, or swap
and mount points should have been definable.

Additional info:

You can get around this and create a mulitple partition >3 installation if
you use ONLY disk druid.  Even there, the inability to specify the
partition you're creating as type "extended" is awkward to work around. 
Creating complex partition schema's in disk druid is not a straightforward

Comment 1 Matt Wilson 2001-07-19 16:03:44 UTC
did you select a filesystem to use for these new partitions?

Comment 2 Richard Forrister 2001-07-19 16:10:45 UTC
All partitions were newly created; all specified as type 83 or type 82.

Comment 3 Glen Foster 2001-07-19 21:11:17 UTC
This defect considered SHOULD-FIX for Fairfax.

Comment 4 Jeremy Katz 2001-07-20 19:37:07 UTC
This should have been one of the things fixed by msf's update disk at
ftp://people.redhat.com/msf/update-disk-07192001.img (or if not, it's done in
internal trees from after that, but I'm pretty certain that it was fixed then)

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