Red Hat Bugzilla – Bug 760243
Support /boot as a Logical Volume
Last modified: 2016-03-22 10:02:28 EDT
grub2 was recently pulled into the distribution including some unsupportable code for handling some limited LVM configurations. Since it seems that people will start to try using this, we should turn it into something that can be supported.
1. Decide precisely what configurations will be supported.
E.g. May have /boot as any LV that is linear or striped, is not a snapshot origin and uses exactly one PV. (I'm *not* saying that is the correct statement yet, but it'll be something along those lines.)
2. Determine what flags/version numbers should be added to LVM to signal that an LV is in that "can be booted from" state and how to set them. Could be set automatically. Could be set using 'lvchange'. Prepare to handle code extensions where it could handle more cases in future and versions of grub2/lvm2 could be mixed. E.g. a GRUB2_BOOTABLE flag or a grub2_bootable_version field set to the first grub2 version number that we know can handle it correctly.
3. Update lvm2 to implement 2.
4. Update grub2 to recognise the state set in 2 and not to attempt to boot from the LV otherwise.
5. Update grub2 to parse the relevant parts of the metadata correctly as per the LVM2 metadata specification. Currently it makes assumptions about the metadata layout (whitespace, field sequences etc.) that are not necessarily true.
6. include LVM in the signed UEFI grubx64.efi
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here: