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.
Hi, there are some good points you raise here. Upgrading an existing RHEL8 system shouldn't generally have this problem because the RHEL8 system will not have a system.devices file, which disables the devices file functionality. Installing a new RHEL9 system with LVM PVs attached should also not have this problem because the installer will run vgimportdevices -a to include existing PVs in the new system. The tricky case, which you've described, is attaching old PVs to a newly installed RHEL9 system (which is using the devices file by default.) In that scenario, we don't want lvm to automatically assume that attached PVs should be used, because often times it's not a correct or safe assumption (e.g. the devices hold guest vm images, in which case the host using them concurrently with the guest may corrupt them.) I'm interested in knowing if or how we could notify users about newly attached PVs that are being ignored by lvm. But, I've struggled to come up with a reasonable way to do that (making it visible and timely, while also not looking outside the devices file to a degree that defeats its purpose.) Although it will be a more common issue in RHEL9, it isn't a completely new issue, because in the past a whitelist-style filter would also silently ignore new PVs.
Thanks for the clarification this makes sense.
The only suggestion would be to make clear the following errors, they do not help unless you already know about the system.devices file.
*****
[root@rhel9 ~]# pvscan --cache /dev/mapper/ldpath04
pvscan[3291] /dev/mapper/ldpath04 excluded by devices file (checking PVID).
..
[root@rhel9 ~]# journalctl -b | grep dm-3
Feb 07 13:41:01 rhel9.lddomain lvm[1124]: /dev/dm-3 excluded by devices file (checking PVID).
*****
The section
excluded by devices file (checking PVID).
could be change to
excluded by /etc/lvm/devices/system.devices
And in /etc/lvm/devices/system.devices
after
# LVM uses devices listed in this file.
add something like
# to maintain this file use the lvmdevices or vgimportdevices commands.
I realize there can be more device files than /etc/lvm/devices/system.devices but if a CU has these they should understand the process.
Have created solution https://access.redhat.com/solutions/6717161 to address this.
If new disks are added and are to be used by lvm "pvscan --cache" should be run anyway and this reports the "excluded by devices file (checking PVID)." for the new disks so I think this is covered! closing the bug.