On Fri, Mar 10, 2017 at 6:24 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
Hello, on my 4.1 environment sometimes I get this kind of message, typically when I create a snapshot. Please note that the snapshot is correctly created: I get the event between the snapshot creation initiated and completed events
VDSM ovmsrv05 command TeardownImageVDS failed: Cannot deactivate Logical Volume: ('General Storage Exception: ("5 [] [\' WARNING: Not using lvmetad because config setting use_lvmetad=0.\', \' WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).\', \' Logical volume 922b5269-ab56-4c4d-838f-49d33427e2ab/79350ec5-eea5-458b-a3ee-ba394d2cda27 in use.\', \' Logical volume 922b5269-ab56-4c4d-838f-49d33427e2ab/3590f38b-1e3b-4170-a901-801ee5d21d59 in use.\']\\n922b5269-ab56-4c4d-838f-49d33427e2ab/[\'3590f38b-1e3b-4170-a901-801ee5d21d59\', \'79350ec5-eea5-458b-a3ee-ba394d2cda27\']",)',)
What is the exact meaning and how can I crosscheck to solve the possible anomaly...? What about lvmetad reference inside the message? Is it an option that in oVirt can be configured or not at all for now?
Can you share the output of: lvs -o vg_name,lv_name,size,attr,devices vgs -o vg_name,pv_name After you get this error. lvmetad is not compatible with ovirt shared storage, this is why you get these warnings. It is disabled in latest 4.1. If you don't want to wait for the release, you can disable it now: systemctl mask lvm2-lvmetad.service lvm2-lvmetad.socket systemctl disable lvm2-lvmetad.service lvm2-lvmetad.socket systemctl stop lvm2-lvmetad.service lvm2-lvmetad.socket Edit /etc/lvm/lvm.conf and set: use_lvmetad = 0 Please report if you still get errors about "Logical volume xxx/yyy in use" after disabling lvmetad. If you do, please file a bug. Nir