Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
LVM2 added a persistent 'skip activation' flag in 2.02.99 (July 2013), and this is automatically set for new thin-provisioned snapshot volumes:
Version 2.02.99 - 24th July 2013
================================
Automatically flag thin snapshots to be skipped during activation.
Add support for persistent flagging of LVs to be skipped during activation.
This prevents users from activating these volumes during boot using the rd.lvm.lv dracut parameter since these volumes will not be activated by 'lvchange' unless the -K/--ignoreactivationskip option is given.
This is inconsistent with the behaviour for 'classic' LVM2 CoW snapshots (since these do not set the activation skip flag by default), and prevents a user from booting the system into a previously created snapshot of the root file system.
Since the user has given the named volume on the kernel command line it is safe to assume that they really intend to activate this device during boot (the boot will fail if the device is actually required anyway).
Version-Release number of selected component (if applicable):
dracut-033-*.el7
How reproducible:
100%
Steps to Reproduce:
1. Install a system to an LVM2 volume group with thin-provisioning enabled for the root volume.
2. Create a thinly provisioned snapshot of the root volume with lvcreate.
3. Attempt to boot the system using root=/dev/$LV_PATH rd.lvm.lv=$LV_PATH
Actual results:
Volume is not activated. Boot fails.
Expected results:
The named logical volume is activated with -K/--ignoreactivationskip
The only way for users to avoid this currently is to either use 'classic' snapshots, or to clear the activation skip flag on each snapshot to be used in this way (which may be undesirable for non-snapshot boot cases).
Additional info:
A PR was submitted to dracut on GitHub to add this capability to the lvm_scan.sh script:
https://github.com/dracutdevs/dracut/pull/223/
That looks fine - the RHEL7 version has two activation commands to cope with older LVM2 versions that do not support the --sysinit option. There also seems to have been some consolidation of LVM argument handling as $lvm_quirk_args.
Adding the -K to both of these should achieve the same result in RHEL7.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:0964
Description of problem: LVM2 added a persistent 'skip activation' flag in 2.02.99 (July 2013), and this is automatically set for new thin-provisioned snapshot volumes: Version 2.02.99 - 24th July 2013 ================================ Automatically flag thin snapshots to be skipped during activation. Add support for persistent flagging of LVs to be skipped during activation. This prevents users from activating these volumes during boot using the rd.lvm.lv dracut parameter since these volumes will not be activated by 'lvchange' unless the -K/--ignoreactivationskip option is given. This is inconsistent with the behaviour for 'classic' LVM2 CoW snapshots (since these do not set the activation skip flag by default), and prevents a user from booting the system into a previously created snapshot of the root file system. Since the user has given the named volume on the kernel command line it is safe to assume that they really intend to activate this device during boot (the boot will fail if the device is actually required anyway). Version-Release number of selected component (if applicable): dracut-033-*.el7 How reproducible: 100% Steps to Reproduce: 1. Install a system to an LVM2 volume group with thin-provisioning enabled for the root volume. 2. Create a thinly provisioned snapshot of the root volume with lvcreate. 3. Attempt to boot the system using root=/dev/$LV_PATH rd.lvm.lv=$LV_PATH Actual results: Volume is not activated. Boot fails. Expected results: The named logical volume is activated with -K/--ignoreactivationskip The only way for users to avoid this currently is to either use 'classic' snapshots, or to clear the activation skip flag on each snapshot to be used in this way (which may be undesirable for non-snapshot boot cases). Additional info: A PR was submitted to dracut on GitHub to add this capability to the lvm_scan.sh script: https://github.com/dracutdevs/dracut/pull/223/