You don't create the brick on the /dev/sd* device

You can see where i create the brick on highlighted multipath device (see attachment), if for some reason you can't do that, you might need to run wipefs -a on it as it probably has some leftover headers from another FS

On 2019-04-25 08:53, Adrian Quintero wrote:

I understand, however the "create brick" option is greyed out (not enabled), the only way I could get that option to be enabled is if I manually edit the multipathd.conf file and add

-------------------------------------------------------------

# VDSM REVISION 1.3
# VDSM PRIVATE
# BEGIN Added by gluster_hci role

blacklist {
        devnode "*"
}
# END Added by gluster_hci role
----------------------------------------------------------

 

Then I go back to the UI and I can use sd* (multpath device).

 

thanks,

On Thu, Apr 25, 2019 at 8:41 AM Alex McWhirter <alex@triadic.us> wrote:

You create the brick on top of the multipath device. Look for one that is the same size as the /dev/sd* device that you want to use.

On 2019-04-25 08:00, Strahil Nikolov wrote:

 

In which menu do you see it this way ?

 

Best Regards,

Strahil Nikolov

 

В сряда, 24 април 2019 г., 8:55:22 ч. Гринуич-4, Adrian Quintero <adrianquintero@gmail.com> написа:

 

 

Strahil,

this is the issue I am seeing now

 

 

The is thru the UI when I try to create a new brick.

 

So my concern is if I modify the filters on the OS what impact will that have after server reboots?

 

thanks,

 

 

On Mon, Apr 22, 2019 at 11:39 PM Strahil <hunter86_bg@yahoo.com> wrote:

I have edited my multipath.conf to exclude local disks , but you need to set '#VDSM private' as per the comments in the header of the file.
Otherwise, use the /dev/mapper/multipath-device notation - as you would do with any linux.

Best Regards,
Strahil NikolovOn Apr 23, 2019 01:07, adrianquintero@gmail.com wrote:
>
> Thanks Alex, that makes more sense now  while trying to follow the instructions provided I see that all my disks /dev/sdb, /dev/sdc, /dev/sdd are locked and inidicating " multpath_member" hence not letting me create new bricks. And on the logs I see
>
> Device /dev/sdb excluded by a filter.\n", "item": {"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}, "msg": "Creating physical volume '/dev/sdb' failed", "rc": 5}
> Same thing for sdc, sdd
>
> Should I manually edit the filters inside the OS, what will be the impact?
>
> thanks again.
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-leave@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/FW3IR3NMQTYZLXBT2VLOCLBKOYJS3MYF/

--

Adrian Quintero

_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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/EW7NKT76JR3TLPP63M7DTDF2TLSMX556/

_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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/XDQFZKYIQGFSAWW5G37ZKRPFLQUXLALJ/

 

 

--

Adrian Quintero