Red Hat Bugzilla – Bug 869264
Cannot specify number of RAID members in GUI
Last modified: 2013-03-12 10:26:30 EDT
Description of problem:
When creating RAID partitioning, there is no option to specify how many RAID members should be created. Anaconda creates one RAID member on each drive. If there are 8 drives in the machine, there will be 8 RAID members.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start graphical installation on a system with 3 or more drives
2. proceed to custom partitioning, select all available drives
3. remove all existing partitions
4. create / mount point, customize it and select Device Type: RAID
5. check "Redundancy (mirror)", uncheck "Optimized performance (stripe)"
6. create /boot and swap partitions and finish the install
RAID members are created on all drives
anaconda allows to specify the number of RAID members
Created attachment 632067 [details]
Created attachment 632068 [details]
Created attachment 632069 [details]
Created attachment 632070 [details]
Since there's no way in UI to specify how many disks to use for RAID device, and this is basic functionality, I would like to propose it as Beta blocker.
11. The installer must be able to create and install to software, hardware or BIOS RAID-0, RAID-1 or RAID-5 partitions for anything except /boot
I disagree. The various checkboxes in the customize section for a mountpoint defines how you can create the various RAID levels, so those are all still creatable.
Yes, they are creatable, but not in a way user wants them... I would rather define where I want it (or at least how much) before anaconda spread it on all available drives, as it's written in description of the bug...
Not in a way *the* user wants them, or not in the way *you* want them? We are trying to do a much different UI design here for partitioning layout, and the existing checkbox design is what we talked about extensively in public.
Going back to the original report here, the reason it put a RAID member on every disk is because you picked every disk to be a part of the installation. If you hadn't done that, we should have only put a RAID member on the disks you specify. I don't see that there is anything to fix in this bug, and suggest it be closed following the blocker meeting.
Chris, imagine that someone would like to create following partitioning on a system with 3 drives:
/boot on sda1
swap on sda2
/ on RAID1 device, members are sdb1 and sdc1
Is it possible to do it without kickstart?
(In reply to comment #9)
> Chris, imagine that someone would like to create following partitioning on a
> system with 3 drives:
> /boot on sda1
> swap on sda2
> / on RAID1 device, members are sdb1 and sdc1
> Is it possible to do it without kickstart?
There is a patch coming soon to f18 to provide a way to select which disks are candidates for a given device. Once this is in place, what you describe above will be as easy to achieve in the GUI as it is in kickstart.
To be clear, what we are going to provide is a way to say "make this device use these disks". For an md array, it means "make the array use all of these disks", while for a partition it means "the partition can end up on any of these disks". In the example above you would select sda and sdb for the md array. Similarly, you could constrain /boot and swap to sda. You can't control the partition numbers, but it will end up as you describe if these are the only devices on the disks.
See bug 870569
*** This bug has been marked as a duplicate of bug 870569 ***