Klemens Kittan wrote:
> Am Wednesday, 20. August 2008 09:43 schrieb Mike Christie:
>> Klemens Kittan wrote:
>>> Am Tuesday, 19. August 2008 19:15 schrieb Mike Christie:
>>>> Klemens Kittan wrote:
>>>>> Am Monday, 18. August 2008 20:10 schrieb Mike Christie:
>>>>>> Klemens Kittan wrote:
>>>>>>> Am Friday, 15. August 2008 20:03 schrieb Mike Christie:
>>>>>>>> Mike Christie wrote:
>>>>>>>>> Klemens Kittan wrote:
>>>>>>>>>> Here is the configuration of my debian kernel (2.6.25-2).
>>>>>>>>> Thanks. It looks like your target is responding to other IO, but
>>>>>>>>> did not respond to the ping quick enough so it timed out. Let me
>>>>>>>>> make a patch for you to test. I should hopefully have it later
>>>>>>>>> today.
>>>>>>>> Try the attached patch over  open-iscsi-2.0-869.2 tarball modules.
>>>>>>>>
>>>>>>>> To apply the patch untar and unzip the source then cd to the dir.
>>>>>>>> Then do:
>>>>>>>>
>>>>>>>> patch -p1 -i where-the-patch-is-saved/relax-ping-timer.patch
>>>>>>>>
>>>>>>>> Then do the normal make and make install. You will probably want to
>>>>>>>> reboot the box to make sure you are using the new modules.
>>>>>>> Unfortunately I got the same errors.
>>>>>> Could you send the log output?
>>>>> Here is the /var/log/syslog.
>>>> Shoot. For some reason that nop is just not finishing in a decent amount
>>>> of time. Could you try the attached patch. It gives the nop even more
>>>> time to complete and it spits out a bunch of debug info to make sure
>>>> open-iscsi did not leak the task.
>>> Unfortunately, the attached file is empty.
>> Oh yeah, if you just log into the target and do not do any IO to the
>> disks. Do you see any messages like this:
>>
>> Aug 14 09:52:23 baltrum kernel: [81064.665749]  connection2:0: ping
>> timeout of
>> 10 secs expired, last rx 4315069195, last ping 4315067926, now 4315070426
>> Aug 14 09:52:23 baltrum kernel: [81064.669756]  connection2:0: detected
>> conn
>> error (1011)
>>
> 
> I get these messages all the time (with and without IO traffic):

you should get these. I am just worried about getting these

 > Aug 20 09:56:10 baltrum kernel: [168687.391990]  connection1:0: ping 
timeout
 > of 10 secs with recv timeout of 5 secs expired last rx 4336967839, 
last ping
 > 4336967081, now 4336970339 task ffff81003797aac0
 > Aug 20 09:56:10 baltrum kernel: [168687.396001]  connection1:0: 
detected conn
 > error (1011)

when there is no IO traffic.

> Aug 20 09:49:13 baltrum kernel: [168482.943791] send ffff8100f9c541c0
> Aug 20 09:49:13 baltrum kernel: [168483.026754] send ffff81003797adc0
> Aug 20 09:49:13 baltrum kernel: [168483.026817] iscsi_free_mgmt_task 
> ffff8100f9c541c0
> Aug 20 09:49:13 baltrum kernel: [168483.031189] iscsi_free_mgmt_task 
> ffff81003797adc0
> Aug 20 09:49:18 baltrum kernel: [168487.772859] send ffff8100f9c54140
> Aug 20 09:49:18 baltrum kernel: [168488.018304] iscsi_free_mgmt_task 
> ffff8100f9c54140
> Aug 20 09:49:18 baltrum kernel: [168488.018342] send ffff81003797aac0
> Aug 20 09:49:18 baltrum kernel: [168488.026632] iscsi_free_mgmt_task 
> ffff81003797aac0
> 
> With IO traffic I get these messages:


Could you give me a large chunk of the log? I need the stuff that 
happened before this part.

> Aug 20 09:56:10 baltrum kernel: [168687.391990]  connection1:0: ping timeout 
> of 10 secs with recv timeout of 5 secs expired last rx 4336967839, last ping 
> 4336967081, now 4336970339 task ffff81003797aac0
> Aug 20 09:56:10 baltrum kernel: [168687.396001]  connection1:0: detected conn 
> error (1011)
> Aug 20 09:56:10 baltrum iscsid: Kernel reported iSCSI connection 1:0 error 
> (1011) state (3)
> Aug 20 09:56:14 baltrum iscsid: connection1:0 is operational after recovery 
> (1 
> attempts)
> 
> Thanks,
> Klemens
> 


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