On 6/29/16, 9:54 AM, "Bart Van Assche" <target-devel-owner@xxxxxxxxxxxxxxx on behalf of bart.vanassche@xxxxxxxxxxx> wrote: On 06/29/2016 04:43 PM, Bryant G. Ly wrote: >> It looks like the masking fixes the device mapper’s ability to find the disk…. > Is the multipath client available in your initrd? If so, running > multipath -ll -v<n> with n >= 3 should reveal why multipathd ignored > certain disks. I enabled it on the initiator: [root@vscsi-bry ~]# multipath -ll [root@vscsi-bry ~]# multipath -ll -v<n> with n >= 3 -bash: n: No such file or directory [root@vscsi-bry ~]# mpathconf multipath is enabled find_multipaths is enabled user_friendly_names is enabled dm_multipath module is loaded multipathd is running [root@vscsi-bry ~]# But it seems to not do much. -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
