Return-Path: X-Sieve: cmu-sieve 2.0 Return-Path: Received: from osgood.ece.cmu.edu (OSGOOD.ECE.CMU.EDU [128.2.129.25]) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h41JLkS02299 for ; Thu, 1 May 2003 15:21:46 -0400 (EDT) Received: by osgood.ece.cmu.edu (Postfix, from userid 953) id 98C5EAF; Thu, 1 May 2003 14:58:53 -0400 (EDT) Received: from sos.ece.cmu.edu (SOS.ECE.CMU.EDU [128.2.129.27]) by osgood.ece.cmu.edu (Postfix) with ESMTP id 1EAFB9B; Thu, 1 May 2003 14:58:51 -0400 (EDT) Received: by sos.ece.cmu.edu (Postfix) id 154BC897C; Thu, 1 May 2003 14:58:34 -0400 (EDT) Received: from sos.ece.cmu.edu (localhost [127.0.0.1]) by sos.ece.cmu.edu (Postfix) with ESMTP id D8424897B for ; Thu, 1 May 2003 14:58:33 -0400 (EDT) Received: (from majordom@localhost) by sos.ece.cmu.edu (8.12.9+Sun/8.12.2/Submit) id h41IwX8o028133 for ips-outgoing; Thu, 1 May 2003 14:58:33 -0400 (EDT) X-Authentication-Warning: sos.ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f X-Original-To: ips@sos.ece.cmu.edu Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23]) by sos.ece.cmu.edu (Postfix) with ESMTP id 5FD61897A for ; Thu, 1 May 2003 14:58:32 -0400 (EDT) Received: by bache.ece.cmu.edu (Postfix) id 01A5B8A; Thu, 1 May 2003 14:58:32 -0400 (EDT) Delivered-To: ips@ece.cmu.edu Received: by bache.ece.cmu.edu (Postfix, from userid 953) id C6F9DC4; Thu, 1 May 2003 14:58:31 -0400 (EDT) Received: from mail.ivivity.com (unknown [64.238.111.99]) by bache.ece.cmu.edu (Postfix) with ESMTP id 37E748A for ; Thu, 1 May 2003 14:58:29 -0400 (EDT) Received: by ATLOPS with Internet Mail Service (5.5.2653.19) id <2CY0SS8H>; Thu, 1 May 2003 14:58:28 -0400 Message-ID: From: Eddy Quicksall To: ips@ece.cmu.edu Subject: clearing SCSI objects Date: Thu, 1 May 2003 14:58:27 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C31013.A662C620" Sender: owner-ips@ece.cmu.edu Precedence: bulk X-Spam-Status: No, hits=-7.7 required=5.0 tests=BAYES_01,HTML_70_80,X_AUTH_WARNING version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C31013.A662C620 Content-Type: text/plain I have a concern regarding a logout followed by login's with a different ISID from the same initiator device. Here is my concern: - the target must keep state information for the initiator port after a logout (such as a reservation - but not limited to that). This is because section F.2 says only an I_T Nexus Loss can effect clearing actions on SCSI objects. - If a target receives a logout, then another login from another initiator (or even another login from the same initiator device but a different ISID) then it must have resources available because it can't clear the SCSI objects from the logged out session. - The resources can become stale and the target could run out of resources. First, am I correct in the above? If not please explain. If this is correct, I have not found anything in the spec that says how long the SCSI objects must be kept around. Eddy ------_=_NextPart_001_01C31013.A662C620 Content-Type: text/html Content-Transfer-Encoding: quoted-printable

I have a concern regarding a logout followed by = login's with a different ISID from the same = initiator device.

Here is my concern:

- the target must keep state = information for the initiator port after a logout (such as a reservation - but not limited to that). This is because section F.2 says only an I_T Nexus = Loss can effect clearing actions on SCSI objects.

- If a target receives a logout, then another = login from another initiator (or even another login from the same initiator = device but a different ISID) then it must have resources available because it = can't clear the SCSI objects from the logged out = session.

- The resources can become stale and the = target could run out of resources.

First, am I correct in the above? If not please = explain.

If this is correct, I have not found anything in the = spec that says how long the SCSI objects must be kept around. =

Eddy

------_=_NextPart_001_01C31013.A662C620--