Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 51907 - disk druid inserts rather than appends software raid sets
disk druid inserts rather than appends software raid sets
Product: Red Hat Public Beta
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Matt Wilson
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2001-08-16 14:39 EDT by Jim Wright
Modified: 2007-04-18 12:35 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-20 11:09:45 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 Jim Wright 2001-08-16 14:39:35 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.6-xfs i686)

Description of problem:
When defining raid sets, disk druid now seems to insert new
raid sets at the front of the queue.  For example, the first thing
I defined the partition for my /boot filesystem.  With nothing else,
this was /dev/md0.  Then I defined the partition for my root filesystem.
After this, /boot became /dev/md1 and root was not /dev/md0.  This is
different from previous behavior.  I prefer having the first raid set
I define be /dev/md0 and stay that way.

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

How reproducible:

Steps to Reproduce:
create more than one software raid set

Additional info:
Comment 1 Michael Fulbright 2001-08-20 11:09:41 EDT
The numbers are pretty arbitrary, so anaconda picks them for the user now.
Comment 2 Matt Wilson 2001-09-05 21:37:51 EDT
I believe that this is fixed.  I did an install with 2 raid0 drives.  I defined
/ first, it became md0.  I defined /usr second, it became md1.
Comment 3 Jim Wright 2001-09-06 12:09:54 EDT
I concur.  Looks fixed in rc2.

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