Not sure if my last message made it through- I don't see it here.

On Dec 17, 9:12 am, Mike Christie <micha...@cs.wisc.edu> wrote:
> Are you using the kernel from CentOS 5.2? If so it has a bug in that
> code patch that you might be hitting. The bug is that the code thought
> the ping timedout when it had not, so the driver would fire off the conn
> error and start recovery when we should not have.


We've been having very similar issues on all six of our CentOS 5.2
machines:

Dec 17 03:23:34 ford kernel: ping timeout of 15 secs expired, last rx
36927101, last ping 36937101, now 36952101
Dec 17 03:23:34 ford kernel: connection1:0: iscsi: detected conn error
(1011)
Dec 17 03:23:35 ford iscsid: Kernel reported iSCSI connection 1:0
error (1011) state (3)
Dec 17 03:23:35 ford kernel: ping timeout of 15 secs expired, last rx
36928014, last ping 36938014, now 36953014
Dec 17 03:23:35 ford kernel: connection2:0: iscsi: detected conn error
(1011)
Dec 17 03:23:36 ford iscsid: Kernel reported iSCSI connection 2:0
error (1011) state (3)
Dec 17 03:24:05 ford iscsid: connect failed (113)


They're running this kernel:
Linux arthur.kyliptix.com 2.6.18-92.1.18.el5PAE #1 SMP Wed Nov 12
10:02:30 EST 2008 i686 i686 i386 GNU/Linux

Is it affected by this?  Anybody have a module I can drop in so I
don't have to recompile? ;)

-John



--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to