linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Christie <michaelc-hcNo3dDEHLuVc3sceRu5cw@public.gmane.org>
To: "Martin K. Petersen"
	<martin.petersen-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: open-iscsi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
	jazz-jYkeLfz6glqHXe+LvDLADg@public.gmane.org,
	linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: iSCSI request keep rejected by microsoft iSCSI target because of write_same check
Date: Wed, 03 Dec 2014 11:08:23 -0600	[thread overview]
Message-ID: <547F4387.5010207@cs.wisc.edu> (raw)
In-Reply-To: <yq17fy9mnsx.fsf-+q57XtR/GgMb6DWv4sQWN6xOck334EZe@public.gmane.org>

On 12/2/14, 9:09 PM, Martin K. Petersen wrote:
>>>>>> "Mike" == Michael Christie <michaelc-hcNo3dDEHLuVc3sceRu5cw@public.gmane.org> writes:
>
> Mike,
>
> Mike> This was the issue we worked with Microsoft on wasn’t it? You guys
> Mike> figured out it was fixed in their target in a recent release
> Mike> right?
>
> The issue we worked recently was wrt. the thin provisioning reporting.
>
> The WRITE SAME problem was that the target returns an iSCSI-specific
> error code rather than a check condition with ILLEGAL REQUEST. You were
> going to talk to MS.

Are you sure about this? The issue you are talking about and the one 
jazz is is the same issue right?

I do not have any of the old replies from MS, but I have some of the 
mails I sent them. It looks like we were asking them about when sd.c 
would send a REPORT SUPPORTED OPERATION, the old MS target would return 
the iscsi specific error code. And it looks like they had us try a 
updated version and in there it was changed to just work on their side.

Jazz-jYkeLfz6glqHXe+LvDLADg@public.gmane.org's patch would work around the same problem because in 
sd_read_write_same, sd would see no_write_same is set and not send 
REPORT SUPPORTED OPERATION.

The subject of that email thread with MS was "Linux iSCSI and Microsoft 
target interop question". I started it with MS on Jan 14, 2014. Vaughan 
ccd you on that thread a little later to get your help. I do not have 
the replies though. I am just going by truncated snippets in mails sent, 
so I do not know what version that was fixed in. Do you guys have the 
replies by any chance?

-- 
You received this message because you are subscribed to the Google Groups "open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to open-iscsi-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.

  parent reply	other threads:[~2014-12-03 17:08 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
     [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 [this message]
     [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=547F4387.5010207@cs.wisc.edu \
    --to=michaelc-hcno3ddehluvc3sceru5cw@public.gmane.org \
    --cc=jazz-jYkeLfz6glqHXe+LvDLADg@public.gmane.org \
    --cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=martin.petersen-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
    --cc=open-iscsi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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 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).