Re: [PATCH 1/1] cxgb3i: Fix a login over vlan issue

Rakesh Ranjan wrote: > Fix a login over vlan issue, when parent interface is vlan and we are using > cxgb3i sepecific > private ip address in '/etc/iscsi/ifaces/' iface file. > > Acked-by: Karen Xie > Signed-off-by: Rakesh Ranjan > --- > drivers/scsi/cxgb3i/cxgb3i_offload.c | 34 > +

RHEL 4 Update 7 + iSCSI + multipath

Hello, This is my first post on this group so please excuse my ignorance. I am using the combination of RHEL, iSCSI and multipath to NetApp SAN. I attach to 9 LUNs. On one path I can connect to all LUNs but on the second path I am unable to see 3 of the 9 LUNs. I have tried 'googleing' but have

SLES10 SP3 x86_64 - connection2:0: detected conn error (1011)

With SLES10 SP3 x86_64, as soon as I start the second iscsi session2, I am very frequently getting the connection errors/ I do not see this with SLES10 SP2 x86_64 on the same setup. Dec 7 18:42:05 cdc-r710s1 kernel: connection2:0: detected conn error (1011) Dec 7 18:42:06 cdc-r710s1 iscsid: con

Re: source code for connection establishment

Jack Z wrote: > Hi all, > > I'm a CS student and I'm trying to understand and locate the source > code for iSCSI connection establishment. But I encountered the > following problem. Could anyone maybe show me where I should go? Any > help would be highly appreciated!! > > 1. I searched in the ent

Re: a deadlock (or corruption) bug in iscsid's logging

guy keren wrote: > Ulrich Windl wrote: >> On 3 Nov 2009 at 2:54, guy keren wrote: >> >>> Hi, >>> >>> the logging code in open-iscsi uses a "logarea" structure in shared >>> memory protected by a SysV semaphore (using semop system calls) - and >>> also places the sembuf array structure used in the

Re: [PATCH] Fix wrong logs in log.c

guy keren wrote: > "Up" and "Down" were wrongly used in semaphore operations. > > Signed-off-by: guy keren > > note: this patch must be applied on top of the previous patch (that > fixes the semop race bug). > Looks ok. Thanks for all the patches! -- You received this message because you ar

Re: [PATCH] do NOT perform illegal operations in a SIGSEGV handler

guy keren wrote: > Ulrich Windl wrote: >> On 24 Nov 2009 at 13:20, guy keren wrote: >> >> [...] >>> by the way - if the system is set to generate core files for daemons, >>> then at least in theory it is possible to write some gdb macros that >>> will extract the non-flushed part of the logs from

Re: [PATCH] Maintain a list of nop-out PDUs that almost timed out

Erez Zilber wrote: > > Maintain a list of nop-out PDUs that almost timed out. > With this information, you can understand and debug the > whole system: you can check your target and see what caused > it to be so slow on that specific time, you can see if your > network was very busy during that ti

Re: [PATCH] Maintain a list of nop-out PDUs that almost timed out

Ulrich Windl wrote: > On 1 Dec 2009 at 14:57, Erez Zilber wrote: > >> Maintain a list of nop-out PDUs that almost timed out. >> With this information, you can understand and debug the >> whole system: you can check your target and see what caused >> it to be so slow on that specific time, you can

Re: Suggestion for new logging mechanism in open-iscsi

Erez Zilber wrote: > I'd like to make some changes in the logging in open-iscsi. The > current status is as follows: > > kernel modules: > > * We use iscsi_cls_session_printk & iscsi_cls_conn_printk in > scsi_transport_iscsi.c. They are sometimes wrapped by macros (e.g. > ISCSI_DBG_TRANS_SESSION)

Re: Unable to apply kernel/2.6.26_compat.patch from git master branch

Yangkook Kim wrote: > Hi, > I just wanted to report a small problem applying kernel/2.6.26_compat.patch > and > provide an updated patch to fix the problem. > Thanks. Sometimes master does not get updated right away because I work from master and the current upstream kernel. It is a pain to fix

Re: SLES10 SP3 x86_64 - connection2:0: detected conn error (1011)

avora wrote: > With SLES10 SP3 x86_64, > as soon as I start the second iscsi session2, I am very frequently > getting the connection errors/ > I do not see this with SLES10 SP2 x86_64 on the same setup. > > Dec 7 18:42:05 cdc-r710s1 kernel: connection2:0: detected conn error > (1011) > Dec 7 18

Another Kernel Oops?

Hi All, I encountered another kernel oops in the open-iscsi code. Not sure if it is fixed in the new code, but I would like to have some idea about it. Thanks. My setup: Ubuntu 8.04 with kernel 2.6.24-24-generic. Open-iscsi 2.0-870.3 The kernel oops happens after my iscsi target node crashed. H

Re: Suggestion for new logging mechanism in open-iscsi

On Mon, Dec 7, 2009 at 7:24 PM, Mike Christie wrote: > Erez Zilber wrote: >> I'd like to make some changes in the logging in open-iscsi. The >> current status is as follows: >> >> kernel modules: >> >> * We use iscsi_cls_session_printk & iscsi_cls_conn_printk in >> scsi_transport_iscsi.c. They are

Re: Another Kernel Oops?

Qinghua(Kevin) Ye wrote: > Hi All, > > I encountered another kernel oops in the open-iscsi code. Not sure if it is > fixed in the new code, but I would like to have some idea about it. Thanks. > What the heck are you running, because I have not seen this oops either :) Is this with the same fai

Re: Suggestion for new logging mechanism in open-iscsi

Erez Zilber wrote: > On Mon, Dec 7, 2009 at 7:24 PM, Mike Christie wrote: >> Erez Zilber wrote: >>> I'd like to make some changes in the logging in open-iscsi. The >>> current status is as follows: >>> >>> kernel modules: >>> >>> * We use iscsi_cls_session_printk & iscsi_cls_conn_printk in >>> scs

Re: Another Kernel Oops?

Thanks Mike. This is not same as before. This time I have a ISCSI connection created successfully between two machine, and network is fine during the creation of connection, and then the other machine crashed due to other reason. I set the noop interval and timeout to be zero. Thanks. Kevin On

[PATCH 1/5] BNX2I - Add 5771E device support to bnx2i driver

* Add code to enumerate 5771E device Signed-off-by: Anil Veerabhadrappa --- drivers/scsi/bnx2i/bnx2i_init.c |6 +- 1 files changed, 5 insertions(+), 1 deletions(-) diff --git a/drivers/scsi/bnx2i/bnx2i_init.c b/drivers/scsi/bnx2i/bnx2i_init.c index 0c4210d..3c46458 100644 --- a/driv

[PATCH 2/5 ] BNX2I - Adjust sq_size module parametr to power of 2 only if a non-zero value is specified

* This issue was discovered during 10G iscsi testing * Default value of 'sq_size' module parameter is '0' which means driver should use predefined SQ queue size when setting up iscsi connection. * roundup_pow_of_two(0) results in '1' and forces driver to setup connect

[PATCH 3/5] BNX2I - update CQ arming algorith for 5771x chipsets

* Only affects 5771x (10G chipsets) devices * This is an optimized CQ arming algoritm which takes into account the number of outstanding tasks Signed-off-by: Anil Veerabhadrappa --- drivers/scsi/bnx2i/bnx2i.h |1 + drivers/scsi/bnx2i/bnx2i_hwi.c | 36 ++

[PATCH 4/5] BNX2I - Task management ABORT TASK fixes

* Due to typo error driver was failing TMF Abort Task request when ctask->sc != NULL. Fixed code to fail TMF ABORT Task request only when ctask->sc == NULL * Clear age component (19 most significant bits) of reference ITT carried in iSCSI TMF PDU. Age component is interna

[PATCH 5/5] BNX2I - minor code cleanup and update driver version

* Removed duplicate function call and not-so-useful comment line Signed-off-by: Anil Veerabhadrappa --- drivers/scsi/bnx2i/bnx2i_init.c |4 ++-- drivers/scsi/bnx2i/bnx2i_iscsi.c |2 -- 2 files changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/scsi/bnx2i/bnx2i_init.c b/