On 06/12/2012 11:45 AM, Mike Christie wrote: > On 06/12/2012 11:41 AM, Mike Christie wrote: >> On 06/12/2012 11:33 AM, awiddersh...@hotmail.com wrote: >>>> This indicates something went screwy. The kernel has that el5 string, so >>>> are you using Centos or RHEL? If so what is the iscsi tools version >>> >>> It is RHEL5 and the tools are as follows: >>> >>> iscsi-initiator-utils-6.2.0.872-13.el5 >>> >>>> Is there anything else in the log before or after that? Something about >>>> a nop or ping timing out? >>> >>> No, it is just went I sent you repeated over and over again. >>> >>>> What type of target is this with? >>> >>> SUN COMSTAR >>> >>>> It could happen if the target is not setting something on the iscsi >>>> packet correctly. To detect this we could take a wireshark/tcpdump trace >>>> and see the packet causing the problem. >>> >>> I doubt this. We have about 300 other hosts connected to this without an >>> issue. >>> >> >> Are those other hosts running the same kernel version and tools as the >> machine you hit this issue with? >> > > If it is easy to replicate, could you send a trace? >
Actually. Do not waste your time. Just update your kernel. There is a bug, because that kernel you are using does not support kernel nops as pings and is returning a different error code than what userspace is expecting when checking if the kernel supports 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-iscsi@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.
