Re: [storm] What if a SCSI Response PDU has GOOD status and a DataSegment?

Julian Satran <julian.satran@gmail.com> Thu, 26 November 2009 09:21 UTC

Return-Path: <julian.satran@gmail.com>
X-Original-To: storm@core3.amsl.com
Delivered-To: storm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6EB3B3A67B0 for <storm@core3.amsl.com>; Thu, 26 Nov 2009 01:21:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_65=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0syvmFjsk6GO for <storm@core3.amsl.com>; Thu, 26 Nov 2009 01:21:55 -0800 (PST)
Received: from mail-bw0-f223.google.com (mail-bw0-f223.google.com [209.85.218.223]) by core3.amsl.com (Postfix) with ESMTP id 2FD803A68BB for <storm@ietf.org>; Thu, 26 Nov 2009 01:21:55 -0800 (PST)
Received: by bwz23 with SMTP id 23so386512bwz.29 for <storm@ietf.org>; Thu, 26 Nov 2009 01:21:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=yJ33G4BUfaGA8eVnfK6fD/1F5K/VaEFln0TkKeK3aFc=; b=mnW9nVWepJfL5EiAHL4uC+j+/03oUU0ZF5HLeoXZgNg6gYpFBK/Zb2wRUOBg0UPBEZ DyKrJvfuACKdZTQAinyXngiWuoFNfWTS2syk5LqpraG2wFnU/C511t6rT31Ac64Q2C77 3qoRGQ5hhPZv8GksfG07Nh2jOZ7Q1zCSkF76k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=XQDDCE+8Hr9v4S8GrY20U2iQZsr/Mq0CdQOxvwdJNceE2kfFr4R2XGKkTiklMbJ+ap W0M0MIwjuTciF8bWiPMWX3uwu6aXKUDrzC/sahoU7vzLu4pw1dybCKZMyDiSEUsZlPb3 e3AAUtwBWRqRk7Qh8yotvKEXPcWcZU0gWUY1g=
Received: by 10.204.150.76 with SMTP id x12mr2433843bkv.30.1259227305945; Thu, 26 Nov 2009 01:21:45 -0800 (PST)
Received: from julo-mbp.xiv.ibm.com (nesher3.haifa.il.ibm.com [192.114.107.4]) by mx.google.com with ESMTPS id 16sm150011fxm.8.2009.11.26.01.21.44 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 26 Nov 2009 01:21:45 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset="us-ascii"
From: Julian Satran <julian.satran@gmail.com>
In-Reply-To: <C2D311A6F086424F99E385949ECFEBCBCA8E5D@CORPUSMX80B.corp.emc.com>
Date: Thu, 26 Nov 2009 11:21:43 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E15870DC-3DFF-4B8F-82C2-18A5248E132D@gmail.com>
References: <4B0C76CF.8070905@ieee.org> <C2D311A6F086424F99E385949ECFEBCBCA8E5D@CORPUSMX80B.corp.emc.com>
To: Black_David@emc.com
X-Mailer: Apple Mail (2.1077)
Cc: storm@ietf.org
Subject: Re: [storm] What if a SCSI Response PDU has GOOD status and a DataSegment?
X-BeenThere: storm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Storage Maintenance WG <storm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/storm>, <mailto:storm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/storm>
List-Post: <mailto:storm@ietf.org>
List-Help: <mailto:storm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/storm>, <mailto:storm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Nov 2009 09:21:56 -0000

David,

The key is a good idea ... but not a great one :-)
As you certainly know there are many storage controllers (targets) on the market that support
iSCSI, FCP, iSER and even several at the same time (for different sessions usually as we and T10 never seriously considered I_T nexi on different transports).

Their SCSI layer (in the ones I know about) is completely transport oblivious so the transport is not really the layer you want to introduce status+sense for statuses other than bad (unit check).

At the SCSI level it may make a lot of sense (no pun intended either).  iSCSI will support it (without any key negotiation being required) as iSCSI does not prohibit it :-). I don't recall exactly what FCP had to say on this but I recall vaguely that there is no explicit interdiction. However some silicon vendors might be "surprised" if it happens.

Regards,
Julo


On 25/11/2009, at 19:57, <Black_David@emc.com> <Black_David@emc.com> wrote:

> [WG chair hat OFF]
> 
> Here's a little more background.  There's an open issue in T10
> about whether sending sense data with GOOD status can just be
> done, vs. whether the target ought to know in advance that
> the initiator is prepared for this.  
> 
> In keeping with the IETF advice to be "conservative in what
> is sent and liberal in what is accepted", if T10 decides not
> to address this at the SCSI level, then it'll be reasonable
> to define an iSCSI negotiation key to indicate that the
> initiator is prepared to accept (in the sense of "tolerate",
> i.e., won't cause an error or worse, rather than any promise
> to "process" or "understand") sense data for GOOD status.
> 
> In addition (as Ralph suggests), it may make sense (pun intended)
> to define this key to cover all status values, not just GOOD,
> even though only GOOD is currently under discussion in T10.
> 
> Thanks,
> --David
> 
> 
>> -----Original Message-----
>> From: storm-bounces@ietf.org [mailto:storm-bounces@ietf.org] 
>> On Behalf Of Ralph Weber
>> Sent: Tuesday, November 24, 2009 7:14 PM
>> To: storm@ietf.org
>> Subject: [storm] What if a SCSI Response PDU has GOOD status 
>> and a DataSegment?
>> 
>> One of the questions that T10 has been wrestling with lately
>> concerns a case where their equivalent of the iSCSI Response
>> PDU contains a status other than CHECK CONDITION and sense
>> data in a Data Segment.
>> 
>> What will initiators do if handed one of these beasts?
>> 
>> Note: GOOD is the current favorite doppelganger for CHECK
>> CONDITION, but BUSY et al. should be considered too when
>> thinking about what initiators might do.
>> 
>> The current belief in T10 is that initiators most likely
>> will ignore any Data Segment found in a Response PDU with
>> GOOD status. This is based on the notion that initiators
>> do not squander the extra cycles needed to validate entire
>> format of a Response PDU.
>> 
>> What do the implementers of iSCSI initiators think?
>> 
>> All the best,
>> 
>> .Ralph
>> 
>> _______________________________________________
>> storm mailing list
>> storm@ietf.org
>> https://www.ietf.org/mailman/listinfo/storm
>> 
>> 
> _______________________________________________
> storm mailing list
> storm@ietf.org
> https://www.ietf.org/mailman/listinfo/storm