-
Bug
-
Resolution: Done-Errata
-
Undefined
-
rhel-9.2.0
-
None
-
lvm2-2.03.23-1.el9
-
None
-
None
-
rhel-sst-logical-storage
-
ssg_filesystems_storage_and_HA
-
23
-
1
-
QE ack, Dev ack
-
False
-
-
None
-
Red Hat Enterprise Linux
-
None
-
None
When a disk level snapshot or clone is created of the OS, it includes /etc/lvm/devices/system.devices which specifies disks that the machine is allowed to use. If the snapshot or clone is restored to a machine with different disks, the system.devices file entries do not match the disks. This prevents lvm from seeing or using the disks. The PVID will be the same, however.
Previous discussion of this problem in bug https://bugzilla.redhat.com/show_bug.cgi?id=2059545
The top proposal so far is to include the the value from /sys/devices/virtual/dmi/id/product_uuid in system.devices. Each lvm command will compare the value in system.devices to the value reported by the machine. If the values do not match, lvm will ignore the IDTYPE/IDNAME values and look for devices using the PVID value. If found, the lvm command will update the IDTYPE/IDNAME values to match the device where the PVID was found.
The intention is to allow other machine-specific identifiers to be added later in case product_uuid is not applicable in some cases.
- links to
-
RHBA-2024:127672 lvm2 update