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

Mike Christie wrote: > Rakesh Ranjan wrote: >> Hi Mike, >> >> Herein attached updated patch based against current open-iscsi head. You >> can simply rename it to 2.6.14-23_compat.patch. >> > > the patch does not work with upstream 2.6.21 and 2.6.23. > > With 2.6.21 i get: > > /home/mnc/open-iscs

iferror codes list

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". --~--~-~--~~~---~--~~ You received this message beca

Re: iscsi-iname command is very misleading

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

Re: iferror codes list

Ciprian Marius Vizitiu (GBIF) wrote: > 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". > The iferror values are just normal

Re: iferror codes list

Mike Christie wrote: > Ciprian Marius Vizitiu (GBIF) wrote: >> 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". >> > > The

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

Hoot, Joseph wrote: > 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,

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

[r...@storage ~]# uname -r 2.6.18-164.el5 [r...@storage ~]# rpm -qa | grep iscsi iscsi-initiator-utils-6.2.0.868-0.18.el5_3.1 [r...@storage ~]# On Nov 10, 2009, at 12:17 PM, Mike Christie wrote: > > Hoot, Joseph wrote: >> I've had about 3 threads of dt (kicking off a bit randomly) on (3) separa

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

On 11/6/09 3:39 PM, "Matthew Dickinson" wrote: > > >> >> Try disabling nops by setting >> >> node.conn[0].timeo.noop_out_interval = 0 >> node.conn[0].timeo.noop_out_timeout = 0 > I'm still getting errors: Nov 10 09:08:04 backup kernel: connection12:0: detected conn error (1011) Nov 10 09

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

Matthew Dickinson wrote: > On 11/6/09 3:39 PM, "Matthew Dickinson" wrote: > >> >>> Try disabling nops by setting >>> >>> node.conn[0].timeo.noop_out_interval = 0 >>> node.conn[0].timeo.noop_out_timeout = 0 > > I'm still getting errors: > > Nov 10 09:08:04 backup kernel: connection12:0: detect

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

Hoot, Joseph wrote: > [r...@storage ~]# uname -r > 2.6.18-164.el5 > [r...@storage ~]# rpm -qa | grep iscsi > iscsi-initiator-utils-6.2.0.868-0.18.el5_3.1 > [r...@storage ~]# > Weird. Is 2.6.18-164.el5 the kernel being used in the virtual machine/DonU? Is that where you are using iscsi? It look

RE: iferror codes list

> > The iferror values are just normal old errnos. -1 is > > > > #define EPERM1 /* Operation not permitted */ > > > > You should get the iferror translated to a string in > /var/log/messages. [...] > Ignore this last part about the log message. The printf and > iferror use