Bug 952121 - RFE: option to created and install to Btrfs raid10 data/metadata profiles
Summary: RFE: option to created and install to Btrfs raid10 data/metadata profiles
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Lehman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: newui-container
Depends On:
Blocks: fedora19rtt
TreeView+ depends on / blocked
 
Reported: 2013-04-15 08:57 UTC by Ľuboš Kardoš
Modified: 2016-08-01 01:26 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-03-13 14:13:36 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Ľuboš Kardoš 2013-04-15 08:57:05 UTC 
Description of problem:
There is no option for BTRFS RAID10 in anaconda GUI.

Version-Release number of selected component (if applicable):
anaconda 19.17-1
fedora 19 alpha RC2

How reproducible:
always

Steps to Reproduce:
1. Start anaconda, proceed to the "MANUAL PARTITIONING" spoke.
2. Create mountpoint.
3. Change "Device Type" from "LVM" to "BTRFS".
4. Activate "RAID Level" selectbox.
  
Actual results:
There are options: "Single (No RAID)", "RAID0 (Performance)", "RAID1 (Redundancy)" in selectbox.

Expected results:
Option "RAID10 (Redundancy, Performance)" also should be in selectbox.


Additional info:
Comment 1 Chris Murphy 2013-05-11 22:56:30 UTC 
This is a regression. It was supported and worked in Fedora 18.
Comment 2 Fedora End Of Life 2013-09-17 07:45:44 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
Comment 3 David Lehman 2015-03-13 14:13:36 UTC 
I think this has been available since at least F21. Feel free to reopen if not. Note that you will need a minimum of four disks to enable this.
Note You need to log in before you can comment on or make changes to this bug.