Description of problem: Creating a raid array is not a one config fits all operation. Use this BZ to review tuneables and parameters used when creating raid arrays from Anaconda. Per BZ#1046725, it is clear that we need to be able to specify chunk size on creation. In addition it is not optimal to default to 1.0 metadata, 1.2 makes more sense. It should also be an option to specify an email address to be put into /etc/mdadm.conf for the raid array BZ#838957 What else?
Are the common/recommended hardware raid companies exposing the necessary information for mkfs to properly align? This is true for md raid and LVM, but if it's still not happening for hardware RAID then we need mkfs options so that proper alignment is possible.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Having a second bug for this isn't helpful. *** This bug has been marked as a duplicate of bug 1046725 ***
Jes, we have some old code that overrides the default for "bootable" arrays (/boot, /boot/efi, PReP) to version 1.0 metadata. It is probably a relic of legacy (v1) grub, but I am not sure. Do you think we can remove this now that we're using grub2?
Grub1 is precisely why that code is there. It was unable to handle any filesystm that didn't start at offset of 0 from the partition table start.
I was going to ask for Doug's input, but he was too quick :) If we're off grub1 for all cases, then lets get rid of it - having an option to allow users to select in an expert many would be preferred, and otherwise default to v1.2. Cheers, Jes
v1.0 metadata is needed for bootable raid1 /boot/efi or UEFI firmware won't be able to use the ESP. I still think that's a misfeature asking for problems, but that bug 1118580 is closed.
One bug per issue is the only way to keep things under control. We're only using v1.0 metadata for /boot/efi as of blivet-1.7. Prior to that change we used v1.0 for /boot, but we've been using v1.2 for everything else for a couple of years now as I recall. Of course, since then we've had a request since then to start using v1.0 for /boot again to accommodate extlinux (https://github.com/rhinstaller/blivet/pull/185).
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
blivet-2.1.0, anaconda-25.5, pykickstart-2.26 contain support for specifying md chunk size. The anaconda support is kickstart-only. Any new support requests for md tuneables should be done in separate bug reports.