On Tue, Sep 4, 2018 at 11:03 PM <g.vasilopoulos(a)uoc.gr&gt; wrote: > after upgrading to 4.20.39-1.el7 sas multipath stopped being detected > I did a diff to the two files > > Is the current behaviour the correct one or the previous one ? > I think sas multipath should also be detected no ? > It should be detect it this is shared storage that you want to use in oVirt It should not be detect if you have local disk using sas. So we really cannot know. [root@g1-car0136 etc]# diff multipath.conf multipath.conf.201809031555 > 1c1 > < # VDSM REVISION 1.6 > --- > > # VDSM REVISION 1.5 > 101,109d100 > < } > < > < # Whitelist FCP and iSCSI devices. > < blacklist { > < protocol ".*" > < } > < > < blacklist_exceptions { > < protocol "(scsi:fcp|scsi:iscsi)" > oVirt does not officially support sas, but this should work: protocol "(scsi:fcp|scsi:iscsi|scsi:sas)" The best way to configure it is to add a dropin configuration file: $ cat /etc/multipath/conf.d/my.conf blacklist_exceptions { protocol "(scsi:fcp|scsi:iscsi|scsi:sas)" }

See also this thread: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/RFEQ5JK2RZM3... I suggest you file a bug for this here: https://bugzilla.redhat.com/enter_bug.cgi?product=vdsm Nir

Le 5 sept. 2018 à 10:23, g.vasilopoulos(a)uoc.gr a écrit : Thank you very much for your answer, somehow the exception did not work, but I guess it is ok it is not a shared storage, it is a dual sas port external JBOD box. I guess multipath is not really needed in that case _______________________________________________ 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/7AC3XX5SSIE...