IETF Logo Mail Archive

Re: [Ips] time-out for R2T PDUs?

Julian Satran <Julian_Satran@il.ibm.com> Thu, 06 November 2008 15:32 UTC

Return-Path: <ips-bounces@ietf.org>
X-Original-To: ips-archive@optimus.ietf.org
Delivered-To: ietfarch-ips-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 324023A6981; Thu, 6 Nov 2008 07:32:12 -0800 (PST)
X-Original-To: ips@core3.amsl.com
Delivered-To: ips@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 26AB13A68C1 for <ips@core3.amsl.com>; Thu, 6 Nov 2008 07:32:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 j-FECNhthRoA for <ips@core3.amsl.com>; Thu, 6 Nov 2008 07:32:10 -0800 (PST)
Received: from mtagate8.de.ibm.com (mtagate8.de.ibm.com [195.212.29.157]) by core3.amsl.com (Postfix) with ESMTP id B1F103A6849 for <ips@ietf.org>; Thu, 6 Nov 2008 07:32:09 -0800 (PST)
Received: from d12nrmr1607.megacenter.de.ibm.com (d12nrmr1607.megacenter.de.ibm.com [9.149.167.49]) by mtagate8.de.ibm.com (8.13.8/8.13.8) with ESMTP id mA6FV7sl617770 for <ips@ietf.org>; Thu, 6 Nov 2008 15:31:07 GMT
Received: from d12av06.megacenter.de.ibm.com (d12av06.megacenter.de.ibm.com [9.149.165.230]) by d12nrmr1607.megacenter.de.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id mA6FV7O84165732 for <ips@ietf.org>; Thu, 6 Nov 2008 16:31:07 +0100
Received: from d12av06.megacenter.de.ibm.com (loopback [127.0.0.1]) by d12av06.megacenter.de.ibm.com (8.13.1/8.13.3) with ESMTP id mA6FV6if006568 for <ips@ietf.org>; Thu, 6 Nov 2008 16:31:06 +0100
Received: from d12mc102.megacenter.de.ibm.com (d12mc102.megacenter.de.ibm.com [9.149.167.114]) by d12av06.megacenter.de.ibm.com (8.13.1/8.12.11) with ESMTP id mA6FV65E006560 for <ips@ietf.org>; Thu, 6 Nov 2008 16:31:06 +0100
In-Reply-To: <ce513bcc0811060714j192cf2cegd7410577c0821a2b@mail.gmail.com>
References: <ce513bcc0811052324u34a89556m6f3e575682781fe8@mail.gmail.com> <8c87b47c0811060116s7cd827f2o820649d1ab08ddbd@mail.gmail.com> <8c87b47c0811060119i355671b7tef114a7f879ea44d@mail.gmail.com> <OFD31AFFD4.C22E4AE9-ON852574F9.004811FC-852574F9.00484925@il.ibm.com> <ce513bcc0811060714j192cf2cegd7410577c0821a2b@mail.gmail.com>
To: Erez Zilber <erezzi.list@gmail.com>
MIME-Version: 1.0
X-KeepSent: FFDF794E:92D4D3FA-852574F9:0054E919; type=4; name=$KeepSent
X-Mailer: Lotus Notes Build V85_09252008 September 25, 2008
From: Julian Satran <Julian_Satran@il.ibm.com>
Message-ID: <OFFFDF794E.92D4D3FA-ON852574F9.0054E919-852574F9.00553D83@il.ibm.com>
Date: Thu, 06 Nov 2008 10:31:02 -0500
X-MIMETrack: Serialize by Router on D12MC102/12/M/IBM(Release 8.0.1|February 07, 2008) at 06/11/2008 17:31:06, Serialize complete at 06/11/2008 17:31:06
Cc: ips@ietf.org
Subject: Re: [Ips] time-out for R2T PDUs?
X-BeenThere: ips@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IP Storage <ips.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ips>
List-Post: <mailto:ips@ietf.org>
List-Help: <mailto:ips-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1176055621=="
Sender: ips-bounces@ietf.org
Errors-To: ips-bounces@ietf.org

The target may try to finish the command with a "check condition" or some 
connection recovery before resorting  to the big hammer.

Julo



From:
"Erez Zilber" <erezzi.list@gmail.com>
To:
Julian Satran/Haifa/IBM@IBMIL
Cc:
"Deva Ranganathan" <deva.ranganathan@gmail.com>, ips@ietf.org
Date:
06/11/2008 10:15
Subject:
Re: [Ips] time-out for R2T PDUs?



There could be a situation in which NOP-IN PDUs from the target are
sent successfully to the initiator, but some bug causes the initiator
not to send the data-out PDU. According to what you say, the target
may decide that it can't wait anymore and logout, right?

Thanks,
Erez

On Thu, Nov 6, 2008 at 3:09 PM, Julian Satran <Julian_Satran@il.ibm.com> 
wrote:
> Correct - there is no standard time-out. Regards, Julo
>
>
> From: "Deva Ranganathan" <deva.ranganathan@gmail.com>
> To: "Erez Zilber" <erezzi.list@gmail.com>
> Cc: ips@ietf.org
> Date: 06/11/2008 04:20
> Subject: Re: [Ips] timeout for R2T PDUs?
> ________________________________
>
>
>
>
> On Thu, Nov 6, 2008 at 2:46 PM, Deva Ranganathan
> <deva.ranganathan@gmail.com> wrote:
> Erez,
>
> I think that this s a target implementation issue wherein the 
implementation
> can choose the timeout  depending on the availability of resources  and 
the
> software architecture. A target also has a NOP-IN sent periodically and 
can
> use this to cleanup  the stale resources as well.
>
> thanks
>
> Deva
> HCL Technologies.
>
>
>
> On Thu, Nov 6, 2008 at 12:54 PM, Erez Zilber <erezzi.list@gmail.com> 
wrote:
> Hi,
>
> I couldn't find an answer to the following question in iSCSI spec:
>
> During the execution of a WRITE command, an R2T PDU is sent from the
> target to the initiator. What should happen if a bug in the initiator
> causes it not to send the data-out PDU? Is there any timeout that will
> allow the target to abort this command?
>
> Thanks,
> Erez
> _______________________________________________
> Ips mailing list
> Ips@ietf.org
> https://www.ietf.org/mailman/listinfo/ips
>
> _______________________________________________
> Ips mailing list
> Ips@ietf.org
> https://www.ietf.org/mailman/listinfo/ips
>
>
>



_______________________________________________
Ips mailing list
Ips@ietf.org
https://www.ietf.org/mailman/listinfo/ips

v2.23.0 | Report a Bug | By Email