Hi,

multipath -ll seems ok. 

root@proxmox-ew-edv-03:~# multipath -ll
vdisk0001 (3600c0ff0001dfcb041cd4e5701000000) dm-7 HP,MSA 2040 SAN
size=11T features='0' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| |- 1:0:0:0 sdc 8:32  active ready running
| `- 2:0:0:0 sdd 8:48  active ready running
`-+- policy='round-robin 0' prio=10 status=enabled
  |- 3:0:0:0 sde 8:64  active ready running
  `- 4:0:0:0 sdf 8:80  active ready running
vdisk0002 (3600c0ff0001e038153cd4e5701000000) dm-8 HP,MSA 2040 SAN
size=4.1T features='0' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| |- 3:0:0:1 sdi 8:128 active ready running
| `- 4:0:0:1 sdj 8:144 active ready running
`-+- policy='round-robin 0' prio=10 status=enabled
  |- 1:0:0:1 sdg 8:96  active ready running
  `- 2:0:0:1 sdh 8:112 active ready running

No Errors in the SAN Log, also no network-link errors on the switch.



-----Ursprüngliche Nachricht-----
Von: pve-user [mailto:[email protected]] Im Auftrag von Emmanuel 
Kasper
Gesendet: Dienstag, 21. Juni 2016 14:01
An: [email protected]
Betreff: Re: [PVE-User] PVE 4.2 multipathing over iscsi problem

Hi Sebastian
I guess /dev/dm-8 your multipath device ? ( You can check that with multipath 
-ll )

>From what I see from your syslog, you have a write error on the multipath 
>device dm-8 and at the same time to the underlying block devices sdc and sdd. 
>Especially if everything is working normally apart from the backups, I don't 
>here think of a multipath configuration problem. So maybe here a network 
>problem ? Can you check form the SAN side if you have a I/O peak when the 
>failure occurs ?

Just to make sure, you're not accessing the same iscsi targets from your other 
cluster ?

Emmanuel


_______________________________________________
pve-user mailing list
[email protected]
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user



_______________________________________________
pve-user mailing list
[email protected]
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Reply via email to