From: Mike Christie <michaelc@cs.wisc.edu>
To: Olaf Kirch <olaf.kirch@oracle.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: iSCSI fun in 2.6.21-rc6
Date: Wed, 18 Apr 2007 12:57:53 -0500 [thread overview]
Message-ID: <46265C21.1070402@cs.wisc.edu> (raw)
In-Reply-To: <46263B7D.5090200@cs.wisc.edu>
Mike Christie wrote:
> Olaf Kirch wrote:
>> Hi,
>>
>> I tried to use the iSCSI initiator with iscsitarget on 2.6.21-rc6 today,
>> with rather mixed results.
>>
>> I could log in okay, and a device would appear. Trying to mount
>> that device would hang though:
>>
>> kernel: iscsi: ctask enq [read cid 0 sc df57e500 cdb 0x28 itt 0x1c len 4096 cmdsn 29 win 33]
>> kernel: iscsi: cmdrsp [op 0x25 cid 0 itt 0x1c len 0]
>> ...
>> kernel: iscsi: ctask enq [read cid 0 sc df57e500 cdb 0x28 itt 0x2b len 4096 cmdsn 44 win 33]
>> kernel: iscsi: cmdrsp [op 0x25 cid 0 itt 0x2b len 0]
>> kernel: kjournald starting. Commit interval 5 seconds
>> kernel: iscsi: ctask enq [write cid 0 sc df57e500 cdb 0x2a itt 0x2c len 4096 cmdsn 45 win 33]
>>
>> Nothing in the logs. tcpdump shows lots of data being transmitted, and tracing
>> iscsitarget shows a storm of data_out commands being received.
>>
>
> Could you send the trace? It is weird that we would get a storm of data
> out commands for a IO that was only 4096 bytes (assuming part of the log
> did not get cut off and the above line is the last one).
Oh yeah, does reverting the endien patches
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-rc-fixes-2.6.git;a=commitdiff;h=b4377356450e2358f5f92d34f130d6cb6574bf76
make any difference?
next prev parent reply other threads:[~2007-04-18 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-18 14:22 iSCSI fun in 2.6.21-rc6 Olaf Kirch
2007-04-18 15:38 ` Mike Christie
2007-04-18 17:57 ` Mike Christie [this message]
2007-04-18 19:02 ` Olaf Kirch
2007-04-18 21:19 ` Mike Christie
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=46265C21.1070402@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=linux-scsi@vger.kernel.org \
--cc=olaf.kirch@oracle.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).