Mike Christie wrote: > avora wrote: >> I do not see ping/nop timeout message in the logs >> (probably that's why changing the noop timeouts did not work). >> Simply starting the session does not cause these errors. >> On starting the second session, I start a daemon >> that does SCSI commands like INQUIRY on all the paths. >> After that I see these messages, and the daemon gets stuck >> for a very long time waiting for SCSI commands to finish. >> >> At the backend I have EMC CLARiiON. >> >> # iscsiadm -m node -P 1 >> Target: iqn.1992-04.com.emc:cx.ckm00091100683.a2 >> Portal: 192.168.10.1:3260,1 >> Iface Name: iface0 >> Target: iqn.1992-04.com.emc:cx.ckm00091100683.b2 >> Portal: 192.168.12.1:3260,3 >> Iface Name: iface1 > > > Does the same path always fail? > > If you log into one can you use it, then if you logout and log into the > other does that other one then work? > > Is there any info the clarrion logs? >
If this is easy to reproduce could you get a wireshark/ethereal trace and send it? -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
