Hi,
investigating what happened during a power failure, I have a small problem
relating the connection numbers found in syslog to the output produced by
iscaiadm: Does the session number (in square brackets) correspond to the
connection number?
i.e. Does tcp: [22] 172.20.77.2:3260,0
Hi,
I'm running a setup of open-iscsi SCST. In order to test error
scenarios during a WRITE command, I've added a delay in SCST, so after
it receives the command, it doesn't send an R2T for 20 seconds. I also
modified the device timeout on the initiator side to 5 seconds.
However, I don't see
On Thu, May 14, 2009 at 2:54 PM, Ulrich Windl
ulrich.wi...@rz.uni-regensburg.de wrote:
On 14 May 2009 at 13:12, Erez Zilber wrote:
Hi,
I'm running a setup of open-iscsi SCST. In order to test error
scenarios during a WRITE command, I've added a delay in SCST, so after
it receives the
Erez Zilber wrote:
Hi,
I'm running a setup of open-iscsi SCST. In order to test error
scenarios during a WRITE command, I've added a delay in SCST, so after
it receives the command, it doesn't send an R2T for 20 seconds. I also
modified the device timeout on the initiator side to 5
On Thu, May 14, 2009 at 5:55 PM, Mike Christie micha...@cs.wisc.edu wrote:
Erez Zilber wrote:
Hi,
I'm running a setup of open-iscsi SCST. In order to test error
scenarios during a WRITE command, I've added a delay in SCST, so after
it receives the command, it doesn't send an R2T for 20
Erez Zilber wrote:
Could you try my linux-2.6-iscsi git tree and turn on debugging?
Moving to another kernel will be harder for me, but I can add a printk
in the eh handler.
Can you recompile the libiscsi module with debugging?
uncomment this:
/* #define DEBUG_SCSI */
in libiscsi.h
sundar mahadevan wrote:
Hi members,
I tried to do the following to find out the error messages:
Both systems with iscsitarget/open-iscsi initiator and open-iscsi
initiator were up.
On the open-iscsi initiator i had opened a terminal with command tail
-f /var/log/messages and left it
@Ulrich,
Were you exporting something on ocfs using the iscsi-target?
If you had meant any data transfer between the boxes using
iscsi-target, there were no data transfers between them.
I tried the suggestion you gave me. It works perfect. Once i stopped
the service, it says connect failed(111)