+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1377157 +++ ====================================================================== Description of problem: The Hypervisor reports errors with devices saying as unknown in pvs output commands with attribute in (m) state. Version-Release number of selected component (if applicable): lvm2-2.02.130-5.el7_2.1.x86_64 How reproducible: Steps to Reproduce: 1. Device is cached in LVM 2. Being skipped during scans 3. pvs reports as unknown device. Actual results: device being reported as unknown though it contains the metadata and volume information on it that can be seen using hexdump . Expected results: The output should contain the device with lvm header for the VG in the output of the command. Additional info: (Originally by Ribu Abraham)
Tal, any idea from the storage side? (Originally by Fabian Deutsch)
Ribu, can you please provide the RHEV-H version used by the customer? (Originally by Fabian Deutsch)
Adam, Nir, any insights? (Originally by Tal Nisan)
Vdsm disable lvm autoback for most commands on RHEV lvs, so you cannot expect the backups to reflect the state on storage. Also, when running lvm commands on RHEL 7, you must disable lvmetad like this: lvs --config ' global { use_lvmetad = 0 }' Or run this before the lvm command: pvscan --cache I'm not sure that sos commands are doing this, so they may display incorrect results. Ribu, can you check that the unexpected output happens when using lvm commands properly? (Originally by Nir Soffer)
In 4.1 vdsm disabled lvmetad, so this issue should be eliminated. The current plan is to backport it to 4.0.z. (Originally by Nir Soffer)
Needs to check this again, I don't think we understand the issue yet. (Originally by Nir Soffer)
(In reply to Nir Soffer from comment #12) > Needs to check this again, I don't think we understand the issue yet. I believe lvmetad disable was backported - anything else? (Originally by Yaniv Kaul)
Based on comment 11, I think we can safely mark this as modified since this looks like another lvmetad issue. (Originally by Nir Soffer)
Kevin, we don't know how to reproduce this issue. You can ask the reporter for instructions, but I don't think it is possible to reproduce this.
Closed based on Comment 18