Return-Path: X-Sieve: cmu-sieve 2.0 Return-Path: Received: (from majordom@localhost) by ece.cmu.edu (8.11.0/8.10.2) id h09IEiZ01085 for ips-outgoing; Thu, 9 Jan 2003 13:14:44 -0500 (EST) X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f Received: from firegate.attotech.com (firegate.attotech.com [12.32.232.50]) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h09IEgW01081 for ; Thu, 9 Jan 2003 13:14:42 -0500 (EST) Received: from [172.16.1.47] by firegate.attotech.com for ips@ece.cmu.edu id MAA24067; Thu Jan 9 12:58:41 2003 Subject: RE: iSCSI: Implicit Termination of Tasks X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: Date: Thu, 9 Jan 2003 12:58:18 -0500 X-MIMETrack: Serialize by Router on NOTESERV1/SERV/ATTO(Release 5.0.8 |June 18, 2001) at 01/09/2003 12:58:18 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii To: ips@ece.cmu.edu From: dcuddihy@attotech.com Sender: owner-ips@ece.cmu.edu Precedence: bulk Forgive me for being confused, but what is the reason for the Check Condition being issued? Say a target implements a blocking CA, (TST 0 Qerr 0) which would disallow other initiator's tasks from running until the check condition could be reported, or another command from the CA'd initiator completes with good status. An internal, non- reported check-condition would cause all other initiators' tasks to be blocked until someone times out and issues a lun reset to the device, or a command from the first initiator completed (not likely, since that initiator logged out and all its tasks have been terminated ). All this caused by bad behavior on behalf of one initiator. Is that what's intended here? Just because someone turns off one machine, all access to that lun is blocked for some period of time? Or did I miss part of the discussion? Implicit termination is handled in FCP without the check condition being issued... all the tasks from the 'logged out' initiator are terminated, reservations cleared, etc. and a UA is generated for that initiator. Every other initiator goes along with no problem, including those sharing the lun with the initiator who abruptly logged out. Seems to work. regards, david cuddihy David J Cuddihy Principal Engineer ATTO Technology, Inc. http://www.attotech.com/fcbridge.html dcuddihy@attotech.com