On Tue, Sep 22, 2020 at 11:23 PM Strahil Nikolov wrote:
>
> In my setup , I got no filter at all (yet, I'm on 4.3.10):
> [root@ovirt ~]# lvmconfig | grep -i filter
We create lvm filter automatically since 4.4.1. If you don't use block storage
(FC, iSCSI) you don't need lvm filter. If you do, you
In my setup , I got no filter at all (yet, I'm on 4.3.10):
[root@ovirt ~]# lvmconfig | grep -i filter
[root@ovirt ~]#
P.S.: Don't forget to 'dracut -f' due to the fact that the initramfs has a
local copy of the lvm.conf
Best Regards,
Strahil Nikolov
В вторник, 22 септември 2020 г.,
On Tue, Sep 22, 2020 at 11:05 PM Jeremey Wise wrote:
>
>
>
> Correct.. on wwid
>
>
> I do want to make clear here. that to geta around the error you must ADD
> (not remove ) drives to /etc/lvm/lvm.conf so oVirt Gluster can complete
> setup of drives.
>
> [root@thor log]# cat
On Tue, Sep 22, 2020 at 10:57 PM Strahil Nikolov wrote:
>
> Obtaining the wwid is not exactly correct.
It is correct - for nvme devices, see:
https://github.com/oVirt/vdsm/blob/353e7b1e322aa02d4767b6617ed094be0643b094/lib/vdsm/storage/lvmfilter.py#L300
This matches the way that multipath lookup
Correct.. on wwid
I do want to make clear here. that to geta around the error you must ADD
(not remove ) drives to /etc/lvm/lvm.conf so oVirt Gluster can complete
setup of drives.
[root@thor log]# cat /etc/lvm/lvm.conf |grep filter
# Broken for gluster in oVirt
#filter =
Obtaining the wwid is not exactly correct.
You can identify them via:
multipath -v4 | grep 'got wwid of'
Short example:
[root@ovirt conf.d]# multipath -v4 | grep 'got wwid of'
Sep 22 22:55:58 | nvme0n1: got wwid of
'nvme.1cc1-324a31313230303131343036-414441544120535838323030504e50-0001'
On Tue, Sep 22, 2020 at 1:50 AM Jeremey Wise wrote:
>
>
> Agree about an NVMe Card being put under mpath control.
NVMe can be used via multipath, this is a new feature added in RHEL 8.1:
https://bugzilla.redhat.com/1498546
Of course when the NVMe device is local there is no point to use it
via
Agree about an NVMe Card being put under mpath control.
I have not even gotten to that volume / issue. My guess is something
weird in CentOS / 4.18.0-193.19.1.el8_2.x86_64 kernel with NVMe block
devices.
I will post once I cross bridge of getting standard SSD volumes working
On Mon, Sep 21,
Why is your NVME under multipath ? That doesn't make sense at all .
I have modified my multipath.conf to block all local disks . Also ,don't forget
the '# VDSM PRIVATE' line somewhere in the top of the file.
Best Regards,
Strahil Nikolov
В понеделник, 21 септември 2020 г., 09:04:28
On Mon, Sep 21, 2020 at 3:30 PM Jeremey Wise wrote:
>
>
> Old System
> Three servers.. Centos 7 -> Lay down VDO (dedup / compression) add those VDO
> volumes as bricks to gluster.
>
> New cluster (remove boot drives and run wipe of all data drives)
>
> Goal: use first 512GB Drives to ignite the
Old System
Three servers.. Centos 7 -> Lay down VDO (dedup / compression) add those
VDO volumes as bricks to gluster.
New cluster (remove boot drives and run wipe of all data drives)
Goal: use first 512GB Drives to ignite the cluster and get things on feet
and stage infrastructure things. Then
On Mon, Sep 21, 2020 at 9:02 AM Jeremey Wise wrote:
>
>
>
>
>
>
> vdo: ERROR - Device /dev/sdc excluded by a filter
>
>
>
>
>
> Other server
>
> vdo: ERROR - Device
> /dev/mapper/nvme.126f-4141303030303030303030303030303032343538-53504343204d2e32205043496520535344-0001p1
> excluded by a
On sobota 19. září 2020 5:58:43 CEST Jeremey Wise wrote:
> [image: image.png]
>
> vdo: ERROR - Device /dev/sdc excluded by a filter
>
> [image: image.png]
when this error happens? When you install ovirt HCI?
> Where is getting this filter.
> I have done gdisk /dev/sdc ( new 1TB Drive) and
Hey!
Can you try editing the lvm cache filter and including sdc multipath into
the filter?
I see that it is missing, and hence the error that sdc is excluded.
Add "a|^/dev/sdc$|" to the lvmfilter and try again.
Thanks
On Mon, Sep 21, 2020 at 11:34 AM Jeremey Wise
wrote:
>
>
>
> [image:
14 matches
Mail list logo
