> Le 4 sept. 2018 à 21:56, Nir Soffer <nsof...@redhat.com> a écrit :
> 
> 

> For reference, I just installed multipath on CentOS:
> 
> # cat /etc/redhat-release 
> CentOS Linux release 7.5.1804 (Core) 
> 
> # rpm -q device-mapper-multipath
> device-mapper-multipath-0.4.9-119.el7_5.1.x86_64
> 
> # lsblk
> NAME                    MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
> sda                       8:0    0   50G  0 disk 
> ├─sda1                    8:1    0    1G  0 part /boot
> └─sda2                    8:2    0   49G  0 part 
>   ├─centos_voodoo4-root 253:0    0 45.1G  0 lvm  /
>   └─centos_voodoo4-swap 253:1    0  3.9G  0 lvm  [SWAP]
> sr0                      11:0    1 1024M  0 rom  
> 
> # multipathd show paths format "%d %P"
> dev protocol   
> sda scsi:unspec
> 
> # man multipath.conf 
> ...
> blacklist section
> ...
>        protocol         Regular expression of the protocol to be excluded. 
> See below for a list of recognized protocols
> ...
>        The  protocol strings that multipath recognizes are scsi:fcp, 
> scsi:spi, scsi:ssa, scsi:sbp, scsi:srp, scsi:iscsi, scsi:sas, scsi:adt, 
> scsi:ata, scsi:unspec, ccw, cciss, nvme, and
>        undef.  The protocol that a path is using can be viewed by running 
> multipathd show paths format "%d %P"
> 

My version:
device-mapper-multipath-0.4.9-119.el7.x86_64

yours:
> device-mapper-multipath-0.4.9-119.el7_5.1.x86_64

So this is quite new.

After a yum update it's much 'better':

~$ sudo multipathd show paths format "%d %P"
dev  protocol   
sddi scsi:unspec
sddj scsi:unspec
sda  scsi:unspec
sdc  scsi:unspec
sdd  scsi:unspec

But as it's not in the blacklist_exceptions, that's what I will need to add.

_______________________________________________
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: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/C2LI5HWVME5SJ2RXJDG2E2PQHWV3G5C6/

Reply via email to