All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: FUJITA Tomonori <tomof@acm.org>
Cc: djiang@mvista.com, linux-scsi@vger.kernel.org,
	fujita.tomonori@lab.ntt.co.jp
Subject: Re: command failing at iSCSI disconnect
Date: Mon, 17 Sep 2007 14:01:17 -0500	[thread overview]
Message-ID: <46EECEFD.5080805@cs.wisc.edu> (raw)
In-Reply-To: <20070914184534G.tomof@acm.org>

FUJITA Tomonori wrote:
> On Fri, 14 Sep 2007 14:43:43 -0700
> Dave Jiang <djiang@mvista.com> wrote:
> 
>> I'm using the latest linus git tree. This is in fileio mode with
>> IOMode=wb. It seems that if I do I/O and then immediately disconnect
>> then the cache sync commands fail. Is this expected behavior or should
>> the connection wait till all existing commands has been flushed before
>> logout? Thanks!
>>
>> root@192.168.1.171:~/iscsi2# iscsiadm -m node -T
>> iqn.2007.com.mvista:disk1 -p 192.168.1.239:3260 --logout
>> Logout session [sd 1:0:0:0: [sdb] Synchronizing SCSI cache
>> sid: 1, target: iqn.2007.com.mvista:disk1, portal: 192.168.1.239,3260]
>> iscsi: cmd 0x35 is not queued (6)
>> iscsi: cmd 0x35 is not queued (6)
>> iscsi: cmd 0x35 is not queued (6)
>> sd 1:0:0:0: [sdb] Result: hostbyte=0x01 driverbyte=0x00
> 
> I think that the fix is in Mike's iscsi git tree.
> 

Yeah, we used to remove the devices from userspace as a workaround, but 
in 2.6.21 doing

echo 1 > /sys/block/sdc/device/delete

changed behavior from where it used to not return until the delete was 
done to where it returns right away.

In my iscsi git tree I finally fixed up the iscsi shutdown code so we do 
not encounter this problem. We did not notice the problem until, 
recently and the fix is larger than what people probably want for stable 
kernels the  so it should hopefully make the next 2.6 kernel.

      reply	other threads:[~2007-09-17 19:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-14 21:43 command failing at iSCSI disconnect Dave Jiang
2007-09-15 17:56 ` FUJITA Tomonori
2007-09-17 19:01   ` Mike Christie [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46EECEFD.5080805@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=djiang@mvista.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tomof@acm.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.