Strahil, In our case the VDO was created during oVirt HCI setup. So I am trying to determine how it gets mounted As far as I can tell this is the config is as follows: [root@host1 ~]# vdo printConfigFile config: !Configuration vdos: vdo_sdc: !VDOService _operationState: finished ackThreads: 1 activated: enabled bioRotationInterval: 64 bioThreads: 4 blockMapCacheSize: 128M blockMapPeriod: 16380 compression: enabled cpuThreads: 2 deduplication: enabled device: /dev/disk/by-id/scsi-3600508b1001cd70935270813aca97c44 hashZoneThreads: 1 indexCfreq: 0 indexMemory: 0.25 indexSparse: disabled indexThreads: 0 logicalBlockSize: 512 logicalSize: 7200G logicalThreads: 1 name: vdo_sdc physicalSize: 781379416K physicalThreads: 1 readCache: enabled readCacheSize: 20M slabSize: 32G writePolicy: auto version: 538380551 filename: /etc/vdoconf.yml [root@host1 ~]# lsblk /dev/sdc NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sdc 8:32 0 745.2G 0 disk ├─3600508b1001cd70935270813aca97c44 253:6 0 745.2G 0 mpath └─vdo_sdc 253:21 0 7T 0 vdo └─gluster_vg_sdc-gluster_lv_data 253:22 0 7T 0 lvm /gluster_bricks/data I know that vdo_sdc is the TYPE="LVM2_member", this from /etc/fstab entries: /dev/mapper/vdo_sdc: UUID="gsaPfw-agoW-HZ3o-ly0W-wjb3-YqvL-266SnR" TYPE="LVM2_member" /dev/mapper/gluster_vg_sdc-gluster_lv_data: UUID="8a94b876-baf2-442c-9e7f-6573308c8ef3" TYPE="xfs" --- Physical volumes --- PV Name /dev/mapper/vdo_sdc PV UUID gsaPfw-agoW-HZ3o-ly0W-wjb3-YqvL-266SnR PV Status allocatable Total PE / Free PE 1843199 / 0 Am am trying to piece things together, I am doing more research on VDO in an HCI oVirt setup. In the meantime any help is welcome. Thanks again, Adrian