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
Hi,
So I wiped everything and went through the wizard to set up hyper converged
Storage & Hosted engine…
Storage was created OK and it went straight on to hosted engine deployment
this failed with the same error…
I have this in vdsm.log
Do you have any idea ?
the system it’s self created the
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
I deployed Gluster FS by first applying the vdo Volume on each host that
Gluster tried to create and failed with
vdo create --name=vdo_sdb --device=/dev/sdb --force
re deploying the gluster wizard then completed without error
___
Users mailing
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
So no Filters in there...
Also Gluster / Engin wizard only shows setup for single node.
I have 3 nodes in Dashboard and have shared passwordless SSH keys between the
host and the other two hosts via the backend Gluster network
___
Users mailing list --
Nope not filters there
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
Check lvm.conf so see if there are any filters set on that device
On Sat, Nov 23, 2019 at 3:27 PM wrote:
> 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
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',
9 matches
Mail list logo
