linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vaughan Cao <vaughan.cao@oracle.com>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	open-iscsi <open-iscsi@googlegroups.com>,
	SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: iSCSI request keep rejected by microsoft iSCSI target because of write_same check
Date: Sat, 11 Jan 2014 09:22:46 +0800	[thread overview]
Message-ID: <52D09CE6.80200@oracle.com> (raw)
In-Reply-To: <52D056E9.8080008@cs.wisc.edu>


On 2014年01月11日 04:24, Mike Christie wrote:
> On 01/10/2014 02:09 AM, vaughan wrote:
>> On 01/10/2014 03:41 PM, Mike Christie wrote:
>>> On 1/10/14 12:11 AM, vaughan wrote:
>>>> I haven't figure out why it's rejected with "bookmark invalid"(9)
>>>> reason, rather than "command not supported". IMO "bookmark invalid" is
>>>> used when minor protocol conflict such as final flag not set with
>>>> non-write command. However, I haven't find error of this kind in
>>>> report_opcode, so I guess it's not supported on the target.
>>>>
>>> Is it possible to get a wireshark/tcpdump trace? It does not have to
>>> be during boot. We just need to see what commands are sent and the
>>> response the target is returning.
>>>
>>> I forgot we know some microsoft iscsi target people. We can just email
>>> them with the trace to confirm what is going on with the target. The
>>> trace seems to be easier for them than them interpreting linux kernel
>>> logs.
>> I enabled debug_iscsi_tcp, here is a more detailed log in normal connection.
>> Does "conn error (1020)" mean it's target peer who disconnect the
>> connection at the same time of reject report_opcode?
> Yes.
>
>> If it is, I think iSCSI boot failure can't be avoided without disable
>> write_same check on OEL.
> Yes, you are right. Due to how more distros do boot, iscsid will not be
> up and you will hang. If are talking about disablement though I think it
> should not be done at the iscsi layer. It should be some sort of
> white/black list at the scsi device layer or something like that.
>
> However, I will ping Microsoft and cc you and we can see what is up for
> sure. Maybe we will get lucky and they will have a release with a fix on
> their side.

Target:
   Windows Server 2008 R2 DataCenter
   Microsoft iSCSI Software Target: 3.3.16563.
Initiator:
   kernel with write_same check in sd, such as Kernel 3.11.10-200.fc19.x86_64

--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-01-11  1:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 10:20 iSCSI request keep rejected by microsoft iSCSI target because of write_same check vaughan
     [not found] ` <52CE77FB.8020100-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2014-01-09 18:38   ` Mike Christie
     [not found]     ` <52CEEC97.8050108-hcNo3dDEHLuVc3sceRu5cw@public.gmane.org>
2014-01-09 22:55       ` The Lee-Man
2014-01-10  1:43     ` Martin K. Petersen
2014-01-10  6:11     ` vaughan
     [not found]       ` <52CF8F0C.3040304-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2014-01-10  7:41         ` Mike Christie
2014-01-10  8:09           ` vaughan
     [not found]             ` <52CFAA9F.5010706-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2014-01-10 20:24               ` Mike Christie
2014-01-11  1:22                 ` Vaughan Cao [this message]
     [not found]                   ` <52D09CE6.80200-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2014-12-01  7:25                     ` jazz-jYkeLfz6glqHXe+LvDLADg
     [not found]                       ` <a90377a8-3ef9-4fc2-a3e9-bfff23560674-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-12-01  9:01                         ` vaughan
     [not found]                           ` <547C2E4D.1030802-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2014-12-01 18:37                             ` Michael Christie
2014-12-03  3:09                               ` Martin K. Petersen
     [not found]                                 ` <yq17fy9mnsx.fsf-+q57XtR/GgMb6DWv4sQWN6xOck334EZe@public.gmane.org>
2014-12-03 17:08                                   ` Mike Christie
     [not found]                                     ` <547F4387.5010207-hcNo3dDEHLuVc3sceRu5cw@public.gmane.org>
2014-12-03 23:00                                       ` Martin K. Petersen
     [not found]                                         ` <yq1fvcwl4oy.fsf-+q57XtR/GgMb6DWv4sQWN6xOck334EZe@public.gmane.org>
2014-12-03 23:49                                           ` Mike Christie
     [not found]                                             ` <547FA18D.7030706-hcNo3dDEHLuVc3sceRu5cw@public.gmane.org>
2014-12-04  2:20                                               ` Martin K. Petersen
     [not found]           ` <52CFA440.7030104-hcNo3dDEHLuVc3sceRu5cw@public.gmane.org>
2014-01-10  8:29             ` vaughan

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=52D09CE6.80200@oracle.com \
    --to=vaughan.cao@oracle.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=michaelc@cs.wisc.edu \
    --cc=open-iscsi@googlegroups.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).