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:
When devices are already present during system startup, we should take advantage of that instead of pretending that each is arriving separately, which is slower and inefficient.
Add fixed point-in-time activation services during system startup that will activate VGs that are already present. After this, switch to event-based activation for VGs that appear later. Often, most VGs will be activated by a single activation command.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
This is roughly a combination of two existing features that would now be used in combination with each other: the activation services (which are currently generated only when event_activation=0) and the lvm2-pvscan services (which are disabled when event_activation=0). The new code adds a temp file that allows for a transition between the two.
(In reply to David Teigland from comment #1)
> This is roughly a combination of two existing features that would now be
> used in combination with each other: the activation services (which are
> currently generated only when event_activation=0) and the lvm2-pvscan
> services (which are disabled when event_activation=0). The new code adds a
> temp file that allows for a transition between the two.
Slight correction, since this is rhel9, the effect is comparable to the combination of generated activation services (lvm2-activation-*) and the event-driven lvm-activation-<vgname> services.
After optimizing vgchange -aay, event based activation is no longer dramatically slower than fixed service activation. Given that, the new activation services in this bz are not planned to be enabled by default. They will still be added as a replacement for the existing activation-generator services (used for event_activation=0.) The new services will enable event activation after they run which the generator services do not.
Pushing the new activation services to 9.1 (replacing the current services from lvm2-activation-generator). The new optimizations to vgchange -aay make the new services less important.