Return-Path: X-Sieve: cmu-sieve 2.0 Return-Path: Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23]) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h4V5ru329376 for ; Sat, 31 May 2003 01:53:56 -0400 (EDT) Received: by bache.ece.cmu.edu (Postfix, from userid 953) id 7919897; Sat, 31 May 2003 01:53:55 -0400 (EDT) Received: from sos.ece.cmu.edu (SOS.ECE.CMU.EDU [128.2.129.27]) by bache.ece.cmu.edu (Postfix) with ESMTP id 9761876; Sat, 31 May 2003 01:53:18 -0400 (EDT) Received: by sos.ece.cmu.edu (Postfix) id EC438894F; Sat, 31 May 2003 01:53:04 -0400 (EDT) Received: from hazard.ece.cmu.edu (HAZARD.ECE.CMU.EDU [128.2.129.24]) by sos.ece.cmu.edu (Postfix) with ESMTP id DE7D8894A for ; Sat, 31 May 2003 01:53:04 -0400 (EDT) Received: by hazard.ece.cmu.edu (Postfix) id A407884; Sat, 31 May 2003 01:53:04 -0400 (EDT) Received: by hazard.ece.cmu.edu (Postfix, from userid 953) id 85D0977; Sat, 31 May 2003 01:53:04 -0400 (EDT) Received: from sos.ece.cmu.edu (SOS.ECE.CMU.EDU [128.2.129.27]) by hazard.ece.cmu.edu (Postfix) with ESMTP id 17D9984 for ; Sat, 31 May 2003 01:53:02 -0400 (EDT) Received: by sos.ece.cmu.edu (Postfix, from userid 363) id E72068950; Sat, 31 May 2003 01:53:01 -0400 (EDT) X-Original-To: ips@sos.ece.cmu.edu Received: from osgood.ece.cmu.edu (OSGOOD.ECE.CMU.EDU [128.2.129.25]) by sos.ece.cmu.edu (Postfix) with ESMTP id 74293894A for ; Sat, 31 May 2003 01:53:00 -0400 (EDT) Received: by osgood.ece.cmu.edu (Postfix) id E84637A; Sat, 31 May 2003 01:52:59 -0400 (EDT) Delivered-To: ips@ece.cmu.edu Received: by osgood.ece.cmu.edu (Postfix, from userid 953) id AB88D87; Sat, 31 May 2003 01:52:59 -0400 (EDT) Received: from d12lmsgate-5.de.ibm.com (d12lmsgate-5.de.ibm.com [194.196.100.238]) by osgood.ece.cmu.edu (Postfix) with ESMTP id 8875E7A for ; Sat, 31 May 2003 01:52:56 -0400 (EDT) Received: from d12relay02.megacenter.de.ibm.com (d12relay02.megacenter.de.ibm.com [9.149.165.196]) by d12lmsgate-5.de.ibm.com (8.12.9/8.12.8) with ESMTP id h4V5qtlr084674; Sat, 31 May 2003 07:52:55 +0200 Received: from d10ml001.telaviv.ibm.com (d10ml001.telaviv.ibm.com [9.148.216.55]) by d12relay02.megacenter.de.ibm.com (8.12.9/NCO/VER6.5) with ESMTP id h4V5qsAj285668; Sat, 31 May 2003 07:52:54 +0200 In-Reply-To: To: "Lakshmi Ramasubramanian" Cc: ips@ece.cmu.edu Subject: Re: iSCSI: Plugging holes in CmdSN MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.0.1 February 07, 2003 From: "Julian Satran" Message-ID: Date: Sat, 31 May 2003 08:52:51 +0300 X-MIMETrack: Serialize by Router on D10ML001/10/M/IBM(Release 5.0.9a |January 7, 2002) at 31/05/2003 08:52:54, Serialize complete at 31/05/2003 08:52:54 Content-Type: multipart/alternative; boundary="=_alternative 001F4AA8C2256D37_=" Sender: owner-ips@ece.cmu.edu Precedence: bulk X-Spam-Status: No, hits=-8.5 required=5.0 tests=BAYES_10,HTML_40_50,HTML_FONT_COLOR_BLUE,IN_REP_TO version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) This is a multipart message in MIME format. --=_alternative 001F4AA8C2256D37_= Content-Type: text/plain; charset="US-ASCII" Yes an initiator can send a reset and have the target completely clear. However bear in mind the recent changes in SPC3 and SAM with regard to support for reset Reset will also clear commands already in execution and (depending on the type of queuing supported) commands from other initiators. Regards, Julo "Lakshmi Ramasubramanian" 30/05/03 22:59 To Julian Satran/Haifa/IBM@IBMIL, cc Subject iSCSI: Plugging holes in CmdSN If the target detects data digest error in a PDU, and sends Reject the initiator * MAY retry the command with the same CmdSN, TaskTag, etc. * Or, Send a Task Mgmt command to ABORT TASK that task. Target will not advance ExpCmdSN until initiator does something to clear the rejected command. But, can the initiator send a Task Mgmt command with function LU Reset (instead of ABORT TASK) as IMMEDIATE command? Should the target then clear the rejected command and any command that was received after that? And, advance the ExpCmdSN so that initiator can proceed with that session? thanks! -lakshmi --=_alternative 001F4AA8C2256D37_= Content-Type: text/html; charset="US-ASCII"
Yes an initiator can send a reset and have the target completely clear. However bear in mind the recent changes in SPC3 and SAM with regard to support for  reset
Reset will also clear commands already in execution and (depending on the type of queuing supported) commands from other initiators.

Regards,
Julo


"Lakshmi Ramasubramanian" <nramas@windows.microsoft.com>

30/05/03 22:59

To
Julian Satran/Haifa/IBM@IBMIL, <ips@ece.cmu.edu>
cc
Subject
iSCSI: Plugging holes in CmdSN





If the target detects data digest error in a PDU,
and sends Reject the initiator
 
 * MAY retry the command with the same CmdSN, TaskTag, etc.
 
 * Or, Send a Task Mgmt command to ABORT TASK that task.
 
Target will not advance ExpCmdSN until initiator does something
to clear the rejected command.
 
But, can the initiator send a Task Mgmt command with function
LU Reset (instead of ABORT TASK) as IMMEDIATE command? Should
the target then clear the rejected command and any command that
was received after that? And, advance the ExpCmdSN so that initiator
can proceed with that session?
 
thanks!
 -lakshmi
 
 
--=_alternative 001F4AA8C2256D37_=--