[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: "Tomasz Chmielewski" <mangoo@xxxxxxxx>, "Fred Blaise" <fred.blaise@xxxxxxxxxxx>
  • From: "Ross S. W. Walker" <rwalker@xxxxxxxxxxxxx>
  • Date: Mon, 5 May 2008 11:47:04 -0400
  • Cc: Xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 05 May 2008 08:48:09 -0700
  • Importance: normal
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Priority: normal
  • Thread-index: AciuxqerQUWdQJcQRFaUa+xvaFhYQQAACqWA
  • Thread-topic: [Xen-users] iscsi conn error: Xen related?

Tomasz Chmielewski wrote:
> 
> 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).

Open-e isn't forth coming to the exact version of IET it uses so I
don't know if it's running the latest, but they heavily patch it
internally, so the code base is diverged. It's kinda like what
Redhat does with their Linux kernels.

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

The OP may want to get a hold of the logs on the Open-e box too in
case there is any hardware failure occurring there.

-Ross

______________________________________________________________________
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.