Full log of point of failure TASK [gluster.infra/roles/backend_setup : Create VDO with specified size] ****** task path: /etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/vdo_create.yml:9 failed: [gfs1.gluster.private] (item={u'writepolicy': u'auto', u'name': u'vdo_sdb', u'readcachesize': u'20M', u'readcache': u'enabled', u'emulate512': u'on', u'logicalsize': u'11000G', u'device': u'/dev/sdb', u'slabsize': u'32G', u'blockmapcachesize': u'128M'}) => {"ansible_loop_var": "item", "changed": false, "err": "vdo: ERROR - Device /dev/sdb excluded by a filter.\n", "item": {"blockmapcachesize": "128M", "device": "/dev/sdb", "emulate512": "on", "logicalsize": "11000G", "name": "vdo_sdb", "readcache": "enabled", "readcachesize": "20M", "slabsize": "32G", "writepolicy": "auto"}, "msg": "Creating VDO vdo_sdb failed.", "rc": 1} failed: [gfs2.gluster.private] (item={u'writepolicy': u'auto', u'name': u'vdo_sdb', u'readcachesize': u'20M', u'readcache': u'enabled', u'emulate512': u'on', u'logicalsize': u'11000G', u'device': u'/dev/sdb', u'slabsize': u'32G', u'blockmapcachesize': u'128M'}) => {"ansible_loop_var": "item", "changed": false, "err": "vdo: ERROR - Device /dev/sdb excluded by a filter.\n", "item": {"blockmapcachesize": "128M", "device": "/dev/sdb", "emulate512": "on", "logicalsize": "11000G", "name": "vdo_sdb", "readcache": "enabled", "readcachesize": "20M", "slabsize": "32G", "writepolicy": "auto"}, "msg": "Creating VDO vdo_sdb failed.", "rc": 1} failed: [gfs3.gluster.private] (item={u'writepolicy': u'auto', u'name': u'vdo_sdb', u'readcachesize': u'20M', u'readcache': u'enabled', u'emulate512': u'on', u'logicalsize': u'11000G', u'device': u'/dev/sdb', u'slabsize': u'32G', u'blockmapcachesize': u'128M'}) => {"ansible_loop_var": "item", "changed": false, "err": "vdo: ERROR - Device /dev/sdb excluded by a filter.\n", "item": {"blockmapcachesize": "128M", "device": "/dev/sdb", "emulate512": "on", "logicalsize": "11000G", "name": "vdo_sdb", "readcache": "enabled", "readcachesize": "20M", "slabsize": "32G", "writepolicy": "auto"}, "msg": "Creating VDO vdo_sdb failed.", "rc": 1} NO MORE HOSTS LEFT ************************************************************* NO MORE HOSTS LEFT ************************************************************* PLAY RECAP ********************************************************************* gfs1.gluster.private : ok=12 changed=1 unreachable=0 failed=1 skipped=9 rescued=0 ignored=0 gfs2.gluster.private : ok=13 changed=2 unreachable=0 failed=1 skipped=9 rescued=0 ignored=0 gfs3.gluster.private : ok=12 changed=1 unreachable=0 failed=1 skipped=9 rescued=0 ignored=0 Please check /var/log/cockpit/ovirt-dashboard/gluster-deployment.log for more informations.

Nope not filters there

Ok so i found that the System was set to MBR ... there are no filters in LVM.conf However disk creation still fails on VDO disk creation with the same error... I have set the disk format to Do you want to proceed? (Y/N): y OK; writing new GUID partition table (GPT) to /dev/sdb. The operation has completed successfully. [root@ovirt2 ~]#

I guess it's filtered because /dev/sdb today is not /dev/sdb after a reboot.You'd better use a persistent name like /dev/disk/by-id/scsi-xxx or anything in /dev/disk/by-id/, /dev/disk/by/uuid/, /dev/disk/by-path/, /dev/disk/by-partuuid/ - as they are supposed to be persistent. Best Regards,Strahil Nikolov В събота, 23 ноември 2019 г., 21:27:38 ч. Гринуич+2, <rob.downer(a)orbitalsystems.co.uk&gt; написа: Gluster fails with vdo: ERROR - Device /dev/sdb excluded by a filter.\n", however I have run [root@ovirt1 ~]# vdo create --name=vdo1 --device=/dev/sdb --force Creating VDO vdo1 Starting VDO vdo1 Starting compression on VDO vdo1 VDO instance 1 volume is ready at /dev/mapper/vdo1 [root@ovirt1 ~]# there are no filters in lvm.conf I have run wipefs -a /dev/sdb —force on all hosts before start _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/RPVWGWIP35Q...

The error message "/dev/sdXX has been excluded by a filter" is potentially very misleading, because it catches all sorts of conditions. Basically any known storage signature on the storage you may recycle (perhaps from a previous attempt) will trigger this. The functionality is more of a feature, it's just the message that could be improved. And then there is simply too many different storage allocation schemes, which LVM tries to recognize all. I have occasionally had to fight hard with dmsetup, because some fluke devmapper signature was still found that lsblk -f, lvs, pvs etc. could not see. I like to use cockpit/storage to test creating volumes before I do another run with the HCI wizard.