On Mon, May 18, 2009 at 4:36 PM, Mike Christie micha...@cs.wisc.edu wrote:
Erez Zilber wrote:
I enabled open-iscsi logging + added some printk calls when the abort
handler returns.
Here's the log. I see that iscsi_eh_cmd_timed_out gets called, but
there's no abort.
May 17 11:00:06 kpc36
Erez Zilber wrote:
On Mon, May 18, 2009 at 4:36 PM, Mike Christie micha...@cs.wisc.edu wrote:
Erez Zilber wrote:
I enabled open-iscsi logging + added some printk calls when the abort
handler returns.
Here's the log. I see that iscsi_eh_cmd_timed_out gets called, but
there's no abort.
May
On Mon, May 18, 2009 at 6:01 PM, Mike Christie micha...@cs.wisc.edu wrote:
Erez Zilber wrote:
On Mon, May 18, 2009 at 4:36 PM, Mike Christie micha...@cs.wisc.edu wrote:
Erez Zilber wrote:
I enabled open-iscsi logging + added some printk calls when the abort
handler returns.
Here's the log.
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
