RE: [linux-iscsi-users] iscsi transmit errors

[Michael S. <mic...@ma...>]

The network connectivity appears to be fine.  When the error occurs I
can ping the iSCSI targets address.  There are no apparent errors on
Linux from ifconfig or ethtool.

While there are a few errors on the network switch, none of the error
counters increment while the iSCSI errors occur.  I've already swapped
out all the network cables as well.  Thanks,

Mike

> -----Original Message-----
> From: N.C.Krishna Murthy [mailto:krm...@ci...]
> Sent: Thursday, April 29, 2004 11:04 PM
> To: Michael Stevens
> Cc: lin...@li...
> Subject: Re: [linux-iscsi-users] iscsi transmit errors
>=20
> Hi,
> 	I am one of the developers of linux iscsi.
>=20
> The messages below suggest network errors/network card error.
> When this problem appears, are you able to atleast  issue a ping
> on the iSCSI target's TargetAddress?
>=20
> Thanx
> N.C.Krishna Murthy
>=20
>=20
> On Friday 30 Apr 2004 4:45 am, Michael Stevens wrote:
> > Hello,
> >
> > I am currently running the linux-iscsi initiator v 4.0.1 on a Debian
> > 'Sarge' system with a 2.6.5 kernel on a dual Xeon.  My network card
is a
> > built in Intel gigabit (e1000 driver).   I can successfully start
the
> > iscsi initiator, find the target, and mount the disk which is being
> > served by an Intransa IP 5000.
> >
> > I am having problems sustaining I/O to the iscsi device.  As a test,
I
> > have put a linux kernel tar ball on my iscsi disk.  I then untar the
tar
> > ball, copy it to another directory, and remove the files.  Someplace
in
> > this whole process (sometimes quickly, sometimes after a few
iterations
> > of this test), the following will appear in syslog:
> >
> > Apr 29 14:03:34 hobson kernel: iSCSI: session iscsi_bus 1 target id
0
> > xmit_data failed to send 65584 bytes, rc 56048
> > Apr 29 14:03:34 hobson kernel: iSCSI: session iscsi bus 1 target id
0 to
> > iqn.2003-12.intransa.com:intransa:mvsn.linux-test dropped
> > Apr 29 14:03:34 hobson kernel: iSCSI: session iscsi bus 1 target id
0 to
> > iqn.2003-12.intransa.com:intransa:mvsn.linux-test waiting 2 seconds
> > before next login attempt
> > Apr 29 14:03:36 hobson kernel: iSCSI: bus 1 target 0 trying to
establish
> > session to portal 0, address 10.11.0.5 port 3260 group 1
> > Apr 29 14:03:36 hobson kernel: iSCSI: bus 1 target 0 established
session
> > #2, portal 0, address 10.11.0.5 port 3260 group 1
> > Apr 29 14:03:36 hobson kernel: iSCSI: session iscsi_bus 1 target id
0
> > xmit_data failed to send 65584 bytes, rc 56432
> > Apr 29 14:03:36 hobson kernel: iSCSI: session iscsi bus 1 target id
0
> > has ended quickly 1 times, login delay 2 seconds
> > Apr 29 14:03:36 hobson kernel: iSCSI: session iscsi bus 1 target id
0 to
> > iqn.2003-12.intransa.com:intransa:mvsn.linux-test dropped
> > Apr 29 14:03:36 hobson kernel: iSCSI: session iscsi bus 1 target id
0 to
> > iqn.2003-12.intransa.com:intransa:mvsn.linux-test waiting 2 seconds
> > before next login attempt
> > Apr 29 14:03:38 hobson kernel: iSCSI: bus 1 target 0 trying to
establish
> > session to portal 0, address 10.11.0.5 port 3260 group 1
> > Apr 29 14:03:38 hobson kernel: iSCSI: bus 1 target 0 established
session
> > #3, portal 0, address 10.11.0.5 port 3260 group 1
> > Apr 29 14:03:38 hobson kernel: iSCSI: session iscsi_bus 1 target id
0
> > xmit_data failed to send 65584 bytes, rc 56432
> > Apr 29 14:03:38 hobson kernel: iSCSI: session iscsi bus 1 target id
0
> > has ended quickly 2 times, login delay 2 seconds
> > Apr 29 14:03:38 hobson kernel: iSCSI: session iscsi bus 1 target id
0 to
> > iqn.2003-12.intransa.com:intransa:mvsn.linux-test dropped
> > Apr 29 14:03:38 hobson kernel: iSCSI: session iscsi bus 1 target id
0 to
> > iqn.2003-12.intransa.com:intransa:mvsn.linux-test waiting 2 seconds
> > before next login attempt
> >
> > This will go on for some variable period of time, after which it
will
> > recover.  Neither ifconfig nor ethtool show any network errors after
the
> > above occurs.  I have updated my network driver, installed v 4.0.1.3
of
> > the iscsi driver, and compiled UP kernels all to no avail :-(.
> >
> > I have windows boxes talking to the Intransa, as well as a RedHat 9
> > system (2.4 kernel and a 3.4.2 linux-iscsi driver), so it seems the
> > iscsi device is working.   Does any one know how to correct this
> > problem?  Thanks in advance,