A storage move/clone/migration may cause LVM "Devices file sys_wwid <wwid> last seen on <devnode> not found"

Issue

• When a storage device used by LVM has the on disk data moved, migrated, or cloned to a new disk at the storage level (other than by pvmove) and the WWID changes, the VG may not activate after the activity or when the system is rebooted.

• Any LVM command complains about missing "not found" and "not matched" device matching when using LVM system.devices cache file:

devices entry /dev/sdb xxxxxxxxxxxxxxxxxxxxxxxxxxxxeMWc devname found but not matched
Match device_id sys_wwid naa.6000xxxxxxxxxxxxxxxxxxxxxxxxx123 to /dev/sda
Match device_id sys_wwid naa.6000xxxxxxxxxxxxxxxxxxxxxxxxx456 to /dev/sdd
Devices file PVID xxxxxxxxxxxxxxxxxxxxxxxxxxxxQh2Y last seen on /dev/sdb not found.
Devices file PVID xxxxxxxxxxxxxxxxxxxxxxxxxxxxwbRY last seen on /dev/sdc not found.
.

• The /etc/lvm/devices/system.devices LVM cache file still has the old, previous, WWID values rather than the new disk's WWID:

# cat etc/lvm/devices/system.devices 
# LVM uses devices listed in this file.
# Created by LVM command vgs pid 1468 at Sun Jun 11 23:38:02 2023
VERSION=1.1.10
IDTYPE=sys_wwid IDNAME=naa.6000xxxxxxxxxxxxx-old-disks-wwid DEVNAME=/dev/sdb PVID=xxx...xxxxQh2Y
IDTYPE=sys_wwid IDNAME=naa.6000xxxxxxxx-previous-disks-wwid DEVNAME=/dev/sdc PVID=xxx...xxxxwbRY