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:
The following copied from bug 1736751:
The lvm commands in initramfs are seeing hundreds of PVs, and dealing with all these extraneous PVs bogs down lvm, preventing it from handling the one (or small number) of PVs that it actually needs to activate the root VG/LV. What we need the installer and dracut to do is create an lvm.conf filter for initramfs that contains *only* the PVs in the VG which holds the root LV. In most cases that VG will contain a single PV, but it could contain several (depending on how the user has created or extended the root VG). Most importantly, it will not contain the PVs for all of the other VGs on the system which are unrelated to booting.
With this filter in place, the next question is what lvm commands the initramfs should run to activate LVs. I believe that what lvm_scan.sh has done in the the past would still work, i.e. run 'lvchange -ay VG/LV' after each PV appears. This will activate LVs for which all PVs are present, and not activate LVs that depend on PVs that have not yet appeared.
We could also look into new ways of having initramfs track which PVs have appeared, and then activating LVs when a VG is complete, but this would add complexity and fragility for little to no benefit, AFAICT, over the method above.
(And speaking of lvm_scan.sh, there is other historical cruft in there that needs to be cleaned up, which we should do at the same time.)
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Comment 1Heinz Mauelshagen
2019-08-19 19:51:50 UTC
Once on this whitelist filtering, we should also tackle root VGs with large numbers of LVs, i.e. limit activation in the initramfs to the list of rd.lvm.lv.
lvm is planning to add the devices file feature in RHEL8 (bug 1922312). The devices file would be the best way to address this bug (limiting devices seen by lvm when it's trying to activate the root LV). A user can edit their initramfs lvm.conf and add a devices file the initramfs to enable this. It's not clear to me yet if we would benefit from new dracut capabilities that make it easier to use the devices file. At some point we might look into adding a dracut command option that would generate an initramfs devices file for the root LV. I'm guessing we'll want some experience using the devices file during boot before we add new options to enable it.
Comment 7RHEL Program Management
2023-09-20 19:50:24 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 8RHEL Program Management
2023-09-20 19:52:15 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.