Return-Path: <owner-ips-outgoing@ece.cmu.edu>
X-Sieve: cmu-sieve 2.0
Return-Path: <owner-ips-outgoing@ece.cmu.edu>
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 h4SNQf327750
	for <ipsml@ece.cmu.edu>; Wed, 28 May 2003 19:26:41 -0400 (EDT)
Received: by bache.ece.cmu.edu (Postfix, from userid 953)
	id E24C089; Wed, 28 May 2003 19:26:40 -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 170EC84; Wed, 28 May 2003 19:26:38 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix)
	id 553E589D7; Wed, 28 May 2003 19:26:21 -0400 (EDT)
Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23])
	by sos.ece.cmu.edu (Postfix) with ESMTP id 32D0C89D6
	for <ips-outgoing@sos.ece.cmu.edu>; Wed, 28 May 2003 19:26:21 -0400 (EDT)
Received: by bache.ece.cmu.edu (Postfix)
	id ECA877A; Wed, 28 May 2003 19:26:20 -0400 (EDT)
Received: by bache.ece.cmu.edu (Postfix, from userid 953)
	id CD33389; Wed, 28 May 2003 19:26:20 -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 3ACB37A
	for <ips-outgoing@ece.cmu.edu>; Wed, 28 May 2003 19:26:15 -0400 (EDT)
Received: by sos.ece.cmu.edu (Postfix, from userid 363)
	id 08DFC89D8; Wed, 28 May 2003 19:26:15 -0400 (EDT)
X-Original-To: ips@sos.ece.cmu.edu
Received: from hazard.ece.cmu.edu (HAZARD.ECE.CMU.EDU [128.2.129.24])
	by sos.ece.cmu.edu (Postfix) with ESMTP id AC40D89D6
	for <ips@sos.ece.cmu.edu>; Wed, 28 May 2003 19:26:13 -0400 (EDT)
Received: by hazard.ece.cmu.edu (Postfix)
	id 205997B; Wed, 28 May 2003 19:26:13 -0400 (EDT)
Delivered-To: ips@ece.cmu.edu
Received: by hazard.ece.cmu.edu (Postfix, from userid 953)
	id 07E9182; Wed, 28 May 2003 19:26:12 -0400 (EDT)
Received: from mxic1.corp.emc.com (unk-for-smtp.isus.emc.com [128.222.32.10])
	by hazard.ece.cmu.edu (Postfix) with ESMTP id D563E7B
	for <ips@ece.cmu.edu>; Wed, 28 May 2003 19:26:10 -0400 (EDT)
Received: by mxic1.corp.emc.com with Internet Mail Service (5.5.2653.19)
	id <L5V6JZQF>; Wed, 28 May 2003 19:26:06 -0400
Message-ID: <277DD60FB639D511AC0400B0D068B71E0564CCB0@corpmx14.corp.emc.com>
From: Black_David@emc.com
To: dcuddihy@attotech.com, ips@ece.cmu.edu
Subject: RE: Tasks Management Actions on Task Sets (10.6.2)
Date: Sat, 24 May 2003 18:01:06 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ips@ece.cmu.edu
Precedence: bulk
X-Spam-Status: No, hits=-8.0 required=5.0
	tests=BAYES_01,DATE_IN_PAST_96_XX,NO_REAL_NAME,QUOTED_EMAIL_TEXT
	version=2.50
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)

> I have a question about the descriptions in 10.6.2, "The target."
> 
> Does this special target handling (wait for all affected 
> iscsi data-phases to complete before passing the task mgmt 
> command to the SCSI layer, plus stat-sn acknowledgment) also 
> apply to the LOGICAL UNIT RESET task management command?

No - that special handling is necessary for things to carry
on cleanly after an ABORT or CLEAR TASK SET.  LOGICAL UNIT
RESET is allowed to be somewhat messier, as it generates a Unit
Attention condition that the Initiator can use to clean up on
its side, whereas ABORT and CLEAR TASK SET do not generate their
own Unit Attention conditions.  A target is not prohibited from
doing the things described in 10.6.2, but the RESET has to
happen regardless of the Initiator's cooperation.

> Can I assume that a lun reset acts like a bunch of abort 
> tasks?  (That's the implication I get from SAM.)

No - that's necessary, but not sufficient - see Section 5.9.7
of SAM-2.  RESET really means reset the LUN to its power-on
condition.  It may be used as part of recovery from an
unexpected situation that the Initiator doesn't understand
how it got into, and hence Target dependence on Initiator
actions to complete the RESET may not be a good idea.

A useful thing to keep in mind is that the design rationale
for any RESET operation defined by SCSI is generally "something's
wrong - put the LU/target back in a known state (power-on-like)
so the Initiator can do something useful".  That's not the
only use of RESETs, but it helps explain their intent.

Thanks,
--David
----------------------------------------------------
David L. Black, Senior Technologist
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
black_david@emc.com        Mobile: +1 (978) 394-7754
----------------------------------------------------
