[PVE-User] PVE 4 -> 5, multipath differences?

[Eneko Lacunza]

Hi,

I see the same behaviour with an EMC VNXe3200 (two priorities).

I assume it is the right thing to do, host really only has 2x1Gbit 
channels to storage... :)

El 7/1/19 a las 10:37, Marco Gaiarin escribió:
> Mandi! Sten Aus
>    In chel di` si favelave...
>
>> As this is my third storage for not critical data, I don't worry much, but I
>> haven't checked if two paths (prio=50) get more load than other two (prio=10).
> Apart from the prio, the differences between jessie multipath is that
> in jessie all path are active (and hwhandler is '0'), while in stretch
> hwhandler is 'ALUA' and only two path are active.
>
> Looking at SCSI path seems al correct: the path active are exactly the
> path where the volume in the SAN reside.
> Looking at code (git master branch) of multipath-tools seems that
> hardware get correctly identified.
>
> So, probably is really the right thing.
>
>
> But also, i've noted that for some strange mean the blacklist in multipath
> does not work as expected. I've:
>
> 	blacklist {
> 	        wwid .*
> 	}
>
> but still i've log full of:
>
> 	Jan  7 09:55:20 ashpool multipathd[470]: sda: spurious uevent, path not found
>
> where SDA is:
>
> 	root at ashpool:~# ls -la /dev/disk/by-id/ | grep sda
> 	lrwxrwxrwx 1 root root    9 gen  7 10:25 scsi-0HP_LOGICAL_VOLUME_00000000 -> ../../sda
> 	lrwxrwxrwx 1 root root   10 gen  7 10:25 scsi-0HP_LOGICAL_VOLUME_00000000-part1 -> ../../sda1
> 	lrwxrwxrwx 1 root root   10 gen  7 10:25 scsi-0HP_LOGICAL_VOLUME_00000000-part2 -> ../../sda2
> 	lrwxrwxrwx 1 root root   10 gen  7 10:25 scsi-0HP_LOGICAL_VOLUME_00000000-part3 -> ../../sda3
> 	lrwxrwxrwx 1 root root    9 gen  7 10:25 scsi-3600508b1001c4972bd1d4906bb1dc75d -> ../../sda
> 	lrwxrwxrwx 1 root root   10 gen  7 10:25 scsi-3600508b1001c4972bd1d4906bb1dc75d-part1 -> ../../sda1
> 	lrwxrwxrwx 1 root root   10 gen  7 10:25 scsi-3600508b1001c4972bd1d4906bb1dc75d-part2 -> ../../sda2
> 	lrwxrwxrwx 1 root root   10 gen  7 10:25 scsi-3600508b1001c4972bd1d4906bb1dc75d-part3 -> ../../sda3
> 	lrwxrwxrwx 1 root root    9 gen  7 10:25 scsi-SHP_LOGICAL_VOLUME_PDNNK0BRH9Z27F -> ../../sda
> 	lrwxrwxrwx 1 root root   10 gen  7 10:25 scsi-SHP_LOGICAL_VOLUME_PDNNK0BRH9Z27F-part1 -> ../../sda1
> 	lrwxrwxrwx 1 root root   10 gen  7 10:25 scsi-SHP_LOGICAL_VOLUME_PDNNK0BRH9Z27F-part2 -> ../../sda2
> 	lrwxrwxrwx 1 root root   10 gen  7 10:25 scsi-SHP_LOGICAL_VOLUME_PDNNK0BRH9Z27F-part3 -> ../../sda3
> 	lrwxrwxrwx 1 root root    9 gen  7 10:25 wwn-0x600508b1001c4972bd1d4906bb1dc75d -> ../../sda
> 	lrwxrwxrwx 1 root root   10 gen  7 10:25 wwn-0x600508b1001c4972bd1d4906bb1dc75d-part1 -> ../../sda1
> 	lrwxrwxrwx 1 root root   10 gen  7 10:25 wwn-0x600508b1001c4972bd1d4906bb1dc75d-part2 -> ../../sda2
> 	lrwxrwxrwx 1 root root   10 gen  7 10:25 wwn-0x600508b1001c4972bd1d4906bb1dc75d-part3 -> ../../sda3
>
> the boot disk, in a hw raid controller.
>
>
> Boh...
>


-- 
Zuzendari Teknikoa / Director Técnico
Binovo IT Human Project, S.L.
Telf. 943569206
Astigarraga bidea 2, 2º izq. oficina 11; 20180 Oiartzun (Gipuzkoa)
www.binovo.es