open-iscsi Google Group

RE: iferror codes list

2009-11-10T19:57:44Z

[...]
Well I was about to suggest that; the only relevant error messages that I
see are:
iscsid: Received iferror -1
iscsid: cannot make a connection to 192.168.1.10:3260 (-1,11)
Which to me is not very informative. :-|
OK, here's the problem: I'm trying to hook a RHEL 5.4 x86_64 running on M610
to an EQL6000XV. I'm way past network problems if only because I can easily

Re: Infortrend + "iSCSI: detected conn error (1011)" + "TCP Dup ACK"

2009-11-10T19:30:18Z

Weird.

Is 2.6.18-164.el5 the kernel being used in the virtual machine/DonU? Is
that where you are using iscsi? It looks like the Oracle enterprise
linux kernel is 2.6.18-164.el5, which looks like it is based on RHEL
5.4. The iscsi code in there is the same as RHEL/upstream. No sendwait
patch.

Re: Infortrend + "iSCSI: detected conn error (1011)" + "TCP Dup ACK"

2009-11-10T17:39:30Z

What version of open-iscsi were you using and what kernel, and were you
using the iscsi kernel modules with open-iscsi.org tarball or from the
kernel?
It looks like we are sending more IO than the target can handle. In one
of those cases it took more than 30 or 60 seconds (depending on your
timeout value).

Re: Infortrend + "iSCSI: detected conn error (1011)" + "TCP Dup ACK"

2009-11-10T17:28:58Z

I'm still getting errors:
Nov 10 09:08:04 backup kernel: connection12:0: detected conn error (1011)
Nov 10 09:08:05 backup iscsid: Kernel reported iSCSI connection 12:0 error
(1011) state (3)
Nov 10 09:08:08 backup iscsid: connection12:0 is operational after recovery
(1 attempts)
Nov 10 09:09:43 backup kernel: connection11:0: detected conn error (1011)

Re: Infortrend + "iSCSI: detected conn error (1011)" + "TCP Dup ACK"

2009-11-10T17:21:08Z

[root@storage ~]# uname -r
2.6.18-164.el5
[root@storage ~]# rpm -qa | grep iscsi
iscsi-initiator-utils-6.2.0.86 8-0.18.el5_3.1
[root@storage ~]#

===========================
Joseph R. Hoot
Lead System Programmer/Analyst
(w) 716-878-4832
(c) 716-759-HOOT
joe.h...@itec.suny.edu
GPG KEY: 7145F633

Re: Infortrend + "iSCSI: detected conn error (1011)" + "TCP Dup ACK"

2009-11-10T17:17:52Z

I think I have the source they are using. Could you do a uname -r, so I
can see what kernel they are using.

Re: iferror codes list

2009-11-10T16:47:21Z

Ignore this last part about the log message. The printf and iferror use
is broken.

Re: iferror codes list

2009-11-10T16:37:13Z

The iferror values are just normal old errnos. -1 is
You should get the iferror translated to a string in /var/log/messages.
Do you see
Received iferror -1: Operation not permitted
?

iferror codes list

2009-11-09T18:41:42Z

Hi everybody,
Is there a list with all the "iferror" codes and their meaning? I'm trying
to use bnx2i on RHEL 5.4 in order to do iSOE on a Dell M610 and a EQL
PS6000XV and from time to time I get "iferror -1".

Re: iscsi-iname command is very misleading

2009-11-10T11:09:13Z

I see two independent steps which we can take:

1. RENAME: IMO that get-iqn can still be interpreted as "get current iqn". In
the SSH spirit, I'd choose iscsi-iqn-gen (like ssh-keygen)

Renaming, of course, might break 3rd party scripts who look for iscsi-iname.

2. Print to STDERR "Generating a new IQN...".

Re: [PATCH] libiscsi back port for RHEL5.{0,1,2,3}/SLES10

2009-11-10T13:59:06Z

Hi mike,
Fixed patch attached.
Regards
Rakesh Ranjan

Re: iscsi-iname command is very misleading

2009-11-10T07:36:48Z

What about naming it "gen-iqn" instead (in the UNIX tradition of having a short
name preferrable over "generate-new-iSCSI-qualified- name-for-initiator")?

Ulrich

Re: Infortrend + "iSCSI: detected conn error (1011)" + "TCP Dup ACK"

2009-11-10T01:13:07Z

I've had about 3 threads of dt (kicking off a bit randomly) on (3) separate volumes for over a week and haven't had a single disconnect yet. I am currently using whatever rpm is distributed with Oracle VM v2.2. I know for sure that they have included the 871 base, plus I believe at least a one off patch. I can get more details if you'd like.

Re: Infortrend + "iSCSI: detected conn error (1011)" + "TCP Dup ACK"

2009-11-09T23:18:57Z

Ah ok. I think it was the patch I sent to Don.

If you just used 871 without the patch (or what is in the stock RHEL 5.4
kernel) does it work ok? There were a couple changes from 868 to 871
that I thought would also fix the problem, so I was waiting for Don and
them to retest just 871 and get back to me.

Re: Infortrend + "iSCSI: detected conn error (1011)" + "TCP Dup ACK"

2009-11-09T19:41:34Z

it was for OiS 871 code prior to RHEL 5.4 release (not sure if the
release include it or not). I'm not sure who came up with it. I was
working with Don Williams from Dell EqualLogic. He got ahold of it
somehow. I applied it and it seemed to improve things.

===========================