# Opennebula try to monitor nonexisting volume groups **URL:** \ **Category:** Product Support\ **Created:** [June 29, 2016, 12:02pm UTC](https://forum.opennebula.io/t/opennebula-try-to-monitor-nonexisting-volume-groups/2481 "2016-06-29T12:02:57Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![feldsam](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/feldsam/32/4441_2.png) [@feldsam](https://forum.opennebula.io/u/feldsam)\ **Post date:** [June 29, 2016, 12:02pm UTC](https://forum.opennebula.io/t/opennebula-try-to-monitor-nonexisting-volume-groups/2481/1 "2016-06-29T12:02:57Z")
Hello, I am using LVM Block storage for IMAGE\_DS and GFS2 for SYSTEM\_DS, FILE\_DS and IMAGE\_DS. Problem is with monitoring scripts. For some time, lvm commands take too long time with errors like this: ```auto Error locking on node X: Command timed out ``` So I try to investigate where is problem and I found locks on non existing volume groups in DLM. ```auto Resource len 10 "V_vg-one-0" Resource len 10 "V_vg-one-1" Resource len 10 "V_vg-one-2" ``` When I look into running processes using `htop` I found that opennebula monitoring scripts are looking for that volume groups `vg-one-0`, `vg-one-1`, `vg-one-2` See attached screenshots: ![](https://canada1.discourse-cdn.com/flex031/uploads/opennebula/original/2X/f/f0f94dddd6d305300901369cd6f46372f066e1ec.png) ![](https://canada1.discourse-cdn.com/flex031/uploads/opennebula/original/2X/3/3ca79b7e47f2f67352d2bb4b209ec8f6551d4af2.png) Why opennebula do this? In `/var/lib/one/remotes/datastore/lvm/lvm.conf I have setuped ```auto # Default volume group VG_NAME=vg-images ``` ```auto [oneadmin@engine1 ~]$ onedatastore list ID NAME SIZE AVAIL CLUSTER IMAGES TYPE DS TM STAT 0 system 1023.9G 98% feldhost 0 sys - shared on 1 default 1023.9G 98% feldhost 5 img fs qcow2 on 2 files 1023.9G 98% feldhost 2 fil fs shared on 104 images 2.4T 25% feldhost 30 img lvm lvm on 106 raid10 2.7T 63% feldhost 0 img lvm lvm on ``` ```auto [oneadmin@engine1 ~]$ onedatastore show 0 DATASTORE 0 INFORMATION ID : 0 NAME : system USER : oneadmin GROUP : oneadmin CLUSTER : feldhost TYPE : SYSTEM DS_MAD : - TM_MAD : shared BASE PATH : /var/lib/one/datastores/0 DISK_TYPE : FILE STATE : READY DATASTORE CAPACITY TOTAL: : 1023.9G FREE: : 1006.2G USED: : 17.7G LIMIT: : - PERMISSIONS OWNER : um- GROUP : u-- OTHER : --- DATASTORE TEMPLATE BASE_PATH="/var/lib/one/datastores/" SHARED="YES" TM_MAD="shared" TYPE="SYSTEM_DS" IMAGES [oneadmin@engine1 ~]$ onedatastore show 1 DATASTORE 1 INFORMATION ID : 1 NAME : default USER : oneadmin GROUP : oneadmin CLUSTER : feldhost TYPE : IMAGE DS_MAD : fs TM_MAD : qcow2 BASE PATH : /var/lib/one/datastores/1 DISK_TYPE : FILE STATE : READY DATASTORE CAPACITY TOTAL: : 1023.9G FREE: : 1006.2G USED: : 17.7G LIMIT: : - PERMISSIONS OWNER : um- GROUP : u-- OTHER : --- DATASTORE TEMPLATE BASE_PATH="/var/lib/one/datastores/" BRIDGE_LIST="node1 node2 node3" CLONE_TARGET="SYSTEM" DISK_TYPE="FILE" DS_MAD="fs" LN_TARGET="NONE" TM_MAD="qcow2" TYPE="IMAGE_DS" IMAGES 71 98 122 124 125 [oneadmin@engine1 ~]$ onedatastore show 2 DATASTORE 2 INFORMATION ID : 2 NAME : files USER : oneadmin GROUP : oneadmin CLUSTER : feldhost TYPE : FILE DS_MAD : fs TM_MAD : shared BASE PATH : /var/lib/one/datastores/2 DISK_TYPE : FILE STATE : READY DATASTORE CAPACITY TOTAL: : 1023.9G FREE: : 1006.2G USED: : 17.7G LIMIT: : - PERMISSIONS OWNER : um- GROUP : u-- OTHER : --- DATASTORE TEMPLATE BASE_PATH="/var/lib/one/datastores/" BRIDGE_LIST="node1 node2 node3" CLONE_TARGET="SYSTEM" DS_MAD="fs" LN_TARGET="NONE" TM_MAD="shared" TYPE="FILE_DS" IMAGES 77 81 [oneadmin@engine1 ~]$ onedatastore show 104 DATASTORE 104 INFORMATION ID : 104 NAME : images USER : oneadmin GROUP : oneadmin CLUSTER : feldhost TYPE : IMAGE DS_MAD : lvm TM_MAD : lvm BASE PATH : /var/lib/one/datastores/104 DISK_TYPE : BLOCK STATE : READY DATASTORE CAPACITY TOTAL: : 2.4T FREE: : 610.3G USED: : 1.8T LIMIT: : - PERMISSIONS OWNER : um- GROUP : u-- OTHER : --- DATASTORE TEMPLATE BASE_PATH="/var/lib/one/datastores/" BRIDGE_LIST="node1 node2 node3" CLONE_TARGET="SELF" DISK_TYPE="BLOCK" DS_MAD="lvm" LN_TARGET="NONE" TM_MAD="lvm" TYPE="IMAGE_DS" VG_NAME="vg-images" IMAGES 18 19 21 25 26 41 42 44 45 52 54 55 56 57 58 59 60 61 64 66 67 68 82 87 90 91 92 93 108 127 [oneadmin@engine1 ~]$ onedatastore show 106 DATASTORE 106 INFORMATION ID : 106 NAME : raid10 USER : oneadmin GROUP : oneadmin CLUSTER : feldhost TYPE : IMAGE DS_MAD : lvm TM_MAD : lvm BASE PATH : /var/lib/one/datastores/106 DISK_TYPE : BLOCK STATE : READY DATASTORE CAPACITY TOTAL: : 2.7T FREE: : 1.7T USED: : 1T LIMIT: : - PERMISSIONS OWNER : um- GROUP : u-- OTHER : --- DATASTORE TEMPLATE BASE_PATH="/var/lib/one/datastores/" BRIDGE_LIST="node1 node2 node3" CLONE_TARGET="SELF" DISK_TYPE="BLOCK" DS_MAD="lvm" LN_TARGET="NONE" TM_MAD="lvm" TYPE="IMAGE_DS" VG_NAME="vg-raid10" IMAGES ``` ---
**Author:** ![denis-ldv](https://avatars.discourse-cdn.com/v4/letter/d/b9bd4f/32.png) [@denis-ldv](https://forum.opennebula.io/u/denis-ldv)\ **Post date:** [June 30, 2016, 11:11am UTC](https://forum.opennebula.io/t/opennebula-try-to-monitor-nonexisting-volume-groups/2481/2 "2016-06-30T11:11:00Z")
We had same problem in our installation. Only solution i found is to comment out lines `if [$? == 0]; then LVM_SIZE_CMD="sudo vgdisplay --separator : --units m -o vg_size,vg_free --nosuffix --noheadings -C" fi` in monitor\_ds.sh. (Opennebula 4.12) ---
**Author:** ![feldsam](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/feldsam/32/4441_2.png) [@feldsam](https://forum.opennebula.io/u/feldsam)\ **Post date:** [June 30, 2016, 2:26pm UTC](https://forum.opennebula.io/t/opennebula-try-to-monitor-nonexisting-volume-groups/2481/3 "2016-06-30T14:26:14Z")
Thank you, looks like it is removed in Opennebula 5.0, so I update from 4.14 to 5.0.1.