WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] iscsi conn error: Xen related?

To: Fred Blaise <fred.blaise@xxxxxxxxxxx>
Subject: Re: [Xen-users] iscsi conn error: Xen related?
From: Tomasz Chmielewski <mangoo@xxxxxxxx>
Date: Mon, 05 May 2008 17:41:28 +0200
Cc: Xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 05 May 2008 08:42:53 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <481F27EB.5030106@xxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <481F27EB.5030106@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.12 (X11/20080305)
Fred Blaise schrieb:
Hello all,

I got some severe iscsi connection loss on my dom0 (Gentoo 2.6.20-xen-r6, xen 3.1.1). Happening several times a day.
open-iscsi version is 2.0.865.12. Target iscsi is the open-e DSS product.

Here is a snip of my messages log file:
May  5 16:52:50 ying connection226:0: iscsi: detected conn error (1011)
May  5 16:52:51 ying iscsid: connect failed (111)
May 5 16:52:51 ying iscsid: Kernel reported iSCSI connection 226:0 error (1011) state (3)
May  5 16:52:53 ying connection215:0: iscsi: detected conn error (1011)
May  5 16:52:53 ying iscsid: connect failed (111)
May  5 16:52:53 ying iscsid: connect failed (111)
May  5 16:52:53 ying iscsid: connect failed (111)
May  5 16:52:53 ying iscsid: connect failed (111)
[...]

and sometimes:
May 5 16:53:11 ying iscsid: connection227:0 is operational after recovery (6 attempts) May 5 16:53:11 ying iscsid: connection221:0 is operational after recovery (6 attempts) May 5 16:53:12 ying iscsid: connection214:0 is operational after recovery (9 attempts)

I doubt it's Xen related.

I'm running lots of dom0s and domUs (and non-Xen) running as iSCSI initiator mostly without such problems.

If it ever happens, it can mean a problem with:

1) iSCSI target implementation,
2) either the target or initiator is very loaded (or both).


Did you try changing the iSCSI target, either to tgt or SCST? I'm not sure what targer you have with e-open; I think they wanted to migrate to SCST, but used buggy IET before (or stil use, I'm not sure).

Any other messages/logs?


2.6.25 has a nice feature with soft lockups detection, i.e. it will print such messages when machine is severely loaded (it may indicate some problems):

May 3 00:46:33 backup1 kernel: INFO: task sync:4875 blocked for more than 120 seconds.


--
Tomasz Chmielewski
http://wpkg.org

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users