< Changes
(→Owner) |
|||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
= Use mdadm for BIOS RAID Support in Anaconda = | = Use mdadm for BIOS RAID Support in Anaconda = | ||
== Summary == | == Summary == | ||
| Line 15: | Line 13: | ||
This should link to your home wiki page so we know who you are. | This should link to your home wiki page so we know who you are. | ||
--> | --> | ||
* Name: [[User:vtrefny| Vojtech Trefny]] (Blivet) | * Name: [[User:vtrefny| Vojtech Trefny]] (Blivet), [[User:vponcova|Vendula Poncova]] (Anaconda) | ||
* Email: vtrefny AT redhat.com, vponcova AT redhat.com | |||
* Email: vponcova AT redhat.com | |||
== Current status == | == Current status == | ||
[[Category: | [[Category:ChangeAcceptedF38]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
| Line 39: | Line 35: | ||
ON_QA -> change is fully code complete | ON_QA -> change is fully code complete | ||
--> | --> | ||
* FESCo issue: | * [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/75I32TSXDAUAWOD64HMG25QY5YHVXJD7/ devel thread] | ||
* Tracker bug: | * FESCo issue: [https://pagure.io/fesco/issue/2922 #2922] | ||
* Release notes tracker: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2158574 #2158574] | ||
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/948 #948] | |||
== Detailed Description == | == Detailed Description == | ||
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | ||
[[Anaconda]] (or to be more precise [[Blivet]], the storage library Anaconda uses) is currently using dmraid to support the BIOS RAID devices (sometimes also called Firmware or | [[Anaconda]] (or to be more precise [[Blivet]], the storage library Anaconda uses) is currently using dmraid to support the BIOS RAID devices (sometimes also called Firmware or Fake RAID) during installation. We plan to replace dmraid by mdadm, which we are currently using for software RAID management. The main reason is that dmraid is no longer actively maintained. mdadm supports the two major BIOS RAID technologies: Common RAID Disk Data Format (DDF) [https://www.snia.org/tech_activities/standards/curr_standards/ddf standard by SNIA] and [https://www.intel.com/content/www/us/en/support/products/122484/memory-and-storage/datacenter-storage-solutions/intel-virtual-raid-on-cpu-intel-vroc.html Intel Matrix Storage Manager] format. mdadm is missing support for some older BIOS RAID formats that existed before DDF and are still supported by dmraid so by implementing this change, we will remove support for some BIOS RAID formats from the installer. | ||
== Feedback == | == Feedback == | ||
| Line 94: | Line 91: | ||
--> | --> | ||
A hardware with BIOS RAID support (DDF or IMSM) is | A hardware with BIOS RAID support (DDF or IMSM) is needed. You can also create a "fake" DDF RAID in a VM with `mdadm` using these two commands: | ||
<code> | |||
mdadm --create /dev/md/ddf --run --level=container --metadata=ddf --raid-disks 2 /dev/sdX /dev/sdY | |||
mdadm --create /dev/md/vol0 --run --level=raid0 --raid-devices=1 /dev/md/ddf --force | |||
</code> | |||
Replace `/dev/sdX` and `/dev/sdY` with two empty disk of the same size. In the installer you should see this array as ''BIOS RAID set'' with the name ''vol0'' in the Installation Destination spoke. Note that since this is a VM an doesn't have the required firmware, the installed system won't boot unless you put `/boot` and bootloader on a separate "normal" disk (but you can still test the installation procedure). | |||
To test the feature simply select the BIOS RAID array as installation target. You follow the QA test case for installing on BIOS/Firmware RAID: [[QA:Testcase_install_to_firmware_RAID]]. | |||
== User Experience == | == User Experience == | ||
Latest revision as of 13:38, 2 February 2023
Use mdadm for BIOS RAID Support in Anaconda
Summary
Use mdadm instead of dmraid to support BIOS RAID (Firmware RAID or Fake RAID) during the Fedora installation process.
Owner
- Name: Vojtech Trefny (Blivet), Vendula Poncova (Anaconda)
- Email: vtrefny AT redhat.com, vponcova AT redhat.com
Current status
- Targeted release: Fedora Linux 38
- Last updated: 2023-02-02
- devel thread
- FESCo issue: #2922
- Tracker bug: #2158574
- Release notes tracker: #948
Detailed Description
Anaconda (or to be more precise Blivet, the storage library Anaconda uses) is currently using dmraid to support the BIOS RAID devices (sometimes also called Firmware or Fake RAID) during installation. We plan to replace dmraid by mdadm, which we are currently using for software RAID management. The main reason is that dmraid is no longer actively maintained. mdadm supports the two major BIOS RAID technologies: Common RAID Disk Data Format (DDF) standard by SNIA and Intel Matrix Storage Manager format. mdadm is missing support for some older BIOS RAID formats that existed before DDF and are still supported by dmraid so by implementing this change, we will remove support for some BIOS RAID formats from the installer.
Feedback
We tried to get feedback from the community to find out how many users use BIOS RAID and would be affected by this change (especially by removing support for the older formats). The only response was from the Fedora QA which has an Intel Matrix machine for testing which should be supported by mdadm.
Benefit to Fedora
Replacing a tool/library that is no longer being actively developed and maintained. Because we are replacing it with a tool that is currently used for software RAID management in the installer, this also means removing one dependency from the installer environment and remove the dmraid startup service from the installed system.
Scope
- Proposal owners: Changes to Blivet (replacing dmraid with mdadm for the specified BIOS RAID formats) and Anaconda (removing the
inst.nodmraidflag)
- Other developers:
- Release engineering: #Releng issue number
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with Objectives:
Upgrade/compatibility impact
This change will affect only new installations (the change only changes behaviour of the installer).
How To Test
A hardware with BIOS RAID support (DDF or IMSM) is needed. You can also create a "fake" DDF RAID in a VM with mdadm using these two commands:
mdadm --create /dev/md/ddf --run --level=container --metadata=ddf --raid-disks 2 /dev/sdX /dev/sdY
mdadm --create /dev/md/vol0 --run --level=raid0 --raid-devices=1 /dev/md/ddf --force
Replace /dev/sdX and /dev/sdY with two empty disk of the same size. In the installer you should see this array as BIOS RAID set with the name vol0 in the Installation Destination spoke. Note that since this is a VM an doesn't have the required firmware, the installed system won't boot unless you put /boot and bootloader on a separate "normal" disk (but you can still test the installation procedure).
To test the feature simply select the BIOS RAID array as installation target. You follow the QA test case for installing on BIOS/Firmware RAID: QA:Testcase_install_to_firmware_RAID.
User Experience
Users with supported BIOS RAIDs shouldn't notice a change, the installation should work the same for them. Users with older unsupported BIOS RAID formats won't be able to install Fedora on these arrays. For these users we'll recommend switching to software RAID.
Dependencies
Contingency Plan
- Contingency mechanism: Revert the changes and keep using dmraid for all BIOS RAID formats.
- Contingency deadline: Beta
- Blocks release? No
Documentation
N/A (not a System Wide Change)