I spent some time this morning trying to find more evidence. As said
only one connection seem to suffer of those connections errors. What
also said however is that only connections with I/O suffer. One thing
bothered me for some time is that the /dev/sdX devices "move around"
when restarting the initiator. To settle this once and for all I read
thought quite a few posts this morning until I finally found one with
a solution. I was unaware of the /dev/disk/by-path devices. By instead
using one of those devices I mounted one lun pointing to the other
connection, and now I see both connection report errors.

tcp: [3] 192.168.43.6:3260,2 iqn.
1994-12.com.promise.target.a9.39.4.55.1.0.0.20
tcp: [4] 192.168.43.5:3260,1 iqn.
1994-12.com.promise.target.a9.39.4.55.1.0.0.20


May 29 09:36:32 manjula klogd:  connection3:0: detected conn error
(1011)
May 29 09:36:33 manjula iscsid: Kernel reported iSCSI connection 3:0
error (1011) state (3)
May 29 09:48:37 manjula klogd:  connection4:0: detected conn error
(1011)
May 29 09:48:38 manjula iscsid: Kernel reported iSCSI connection 4:0
error (1011) state (3)
May 29 09:49:11 manjula klogd:  connection4:0: detected conn error
(1011)
May 29 09:49:12 manjula iscsid: Kernel reported iSCSI connection 4:0
error (1011) state (3)

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~----------~----~----~----~------~----~------~--~---

Reply via email to