Hi all,
I am working on iSCSI En. Tar. Could you please someone explain about the
performance of the IET.
If so how the performance was calculated and what was the througput for the
same.
Thanks
Gopala krishnan Varatharajan
On Sat, Nov 7, 2009 at 3:09 AM, Matthew Dickinson <
matt-openis...@alpha345.com> wrote:
>
> On 11/6/09 3:08 PM, "Mike Christie" <micha...@cs.wisc.edu> wrote:
>
> >
> > Could you send more of the log? Do you see a message like
> > connection1:0 is
> > operational after recovery (1 attempts)
> > after you see the conn errors (how many attempts)?
>
> Here's one particular connection:
>
> Nov 4 05:12:14 backup kernel: connection22:0: ping timeout of 5 secs
> expired, recv timeout 5, last rx 4321648393, last ping 4321653393, now
> 4321658393
> Nov 4 05:12:14 backup kernel: connection22:0: detected conn error (1011)
> Nov 4 05:12:21 backup iscsid: connection22:0 is operational after recovery
> (1 attempts)
> Nov 4 05:12:46 backup kernel: connection22:0: ping timeout of 5 secs
> expired, recv timeout 5, last rx 4321680691, last ping 4321685691, now
> 4321690691
> Nov 4 05:12:46 backup kernel: connection22:0: detected conn error (1011)
> Nov 4 05:12:58 backup iscsid: connection22:0 is operational after recovery
> (1 attempts)
> Nov 4 07:46:03 backup kernel: connection22:0: ping timeout of 5 secs
> expired, recv timeout 5, last rx 4330877890, last ping 4330882890, now
> 4330887890
> Nov 4 07:46:03 backup kernel: connection22:0: detected conn error (1011)
> Nov 4 07:46:10 backup iscsid: connection22:0 is operational after recovery
> (1 attempts)
> Nov 4 07:46:27 backup kernel: connection22:0: ping timeout of 5 secs
> expired, recv timeout 5, last rx 4330901733, last ping 4330906733, now
> 4330911733
> Nov 4 07:46:27 backup kernel: connection22:0: detected conn error (1011)
> Nov 4 07:46:32 backup iscsid: connection22:0 is operational after recovery
> (1 attempts)
> Nov 4 07:47:21 backup kernel: connection22:0: ping timeout of 5 secs
> expired, recv timeout 5, last rx 4330955414, last ping 4330960414, now
> 4330965414
> Nov 4 07:47:21 backup kernel: connection22:0: detected conn error (1011)
> Nov 4 07:47:28 backup iscsid: connection22:0 is operational after recovery
> (1 attempts)
> Nov 4 07:48:28 backup kernel: connection22:0: ping timeout of 5 secs
> expired, recv timeout 5, last rx 4331023213, last ping 4331028213, now
> 4331033213
> Nov 4 07:48:28 backup kernel: connection22:0: detected conn error (1011)
> Nov 4 07:48:35 backup iscsid: connection22:0 is operational after recovery
> (1 attempts)
>
> FWIW:
>
> [r...@backup ~]# cat /var/log/messages | grep "after recovery" | awk
> '{print
> $11" "$12}' | sort | uniq
> (113 attempts)
> (1 attempts)
> (24 attempts)
> (2 attempts)
> (3 attempts)
> (4 attempts)
> (5 attempts)
> (66 attempts)
> (68 attempts)
> (6 attempts)
> (7 attempts)
> (8 attempts)
> (9 attempts)
>
> >
> > Try disabling nops by setting
> >
> > node.conn[0].timeo.noop_out_interval = 0
> > node.conn[0].timeo.noop_out_timeout = 0
>
> Ok, I'll let you know how it pans out.
>
> Thanks,
>
> Matthew
>
>
>
> >
>
--
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
