OLVM: All Storage Domain Operations Fail After Cloning a Direct LUN
(Doc ID 2805600.1)
Last updated on MARCH 22, 2023
Applies to:
Linux OS - Version Oracle Linux 7.9 with Unbreakable Enterprise Kernel [5.4.17] and laterLinux x86-64
Symptoms
After cloning a direct LUN all operations like create/delete/move disk fail.
All LVM related messages in VDSM show errors and any LVM scan command will exit with a status=5.
In vdsm log file:
2021-10-10 00:00:00,000+0 DEBUG (tasks/6) [storage.Misc.excCmd] FAILED: <err> = ' Scan of VG volg from /dev/mapper/36001405269b455786aa4ccd99683bc56 found metadata seqno 3 vs previous 2.\n WARNING: Not using device /dev/mapper/36001405269b455786aa4ccd99683bc56 for PV e505253f-3bba-41d5-b273-b8412a8d03e2.\n WARNING: PV e505253f-3bba-41d5-b273-b8412a8d03e2 prefers device/dev/mapper/36001405269b455786aa4ccd99683bc44 because device was seen first.\n Scan of VG volg from /dev/mapper/36001405a2a6f8c4fb5244f984af17519 found metadata seqno 3 vs previous 2.\n Scan of VG volg from /dev/mapper/36001405269b455786aa4ccd99683bc56 found metadata seqno 3 vs previous 2.\n Recovery of volume group "volg" failed.\n Cannot process volume group volg\n'; <rc> = 5 (commands:219)
Changes
VM Direct attached LUNs are being cloned on the Storage side and presented to other VMs running in the same environment.
For a specific VM, it was necessary to increase the LUN size and Volume Group.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |