IETF Logo Mail Archive

Re: [nfsv4] question on bulk recall text

Trond Myklebust <Trond.Myklebust@netapp.com> Tue, 12 October 2010 16:59 UTC

Return-Path: <Trond.Myklebust@netapp.com>
X-Original-To: nfsv4@core3.amsl.com
Delivered-To: nfsv4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E43963A6910 for <nfsv4@core3.amsl.com>; Tue, 12 Oct 2010 09:59:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.492
X-Spam-Level:
X-Spam-Status: No, score=-6.492 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, 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 dgB4mOcl-utn for <nfsv4@core3.amsl.com>; Tue, 12 Oct 2010 09:59:10 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by core3.amsl.com (Postfix) with ESMTP id 290693A6876 for <nfsv4@ietf.org>; Tue, 12 Oct 2010 09:59:10 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.57,320,1283756400"; d="scan'208";a="466451316"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 12 Oct 2010 10:00:24 -0700
Received: from sacrsexc1-prd.hq.netapp.com (sacrsexc1-prd.hq.netapp.com [10.99.115.27]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id o9CGxxIf004223; Tue, 12 Oct 2010 10:00:23 -0700 (PDT)
Received: from SACMVEXC2-PRD.hq.netapp.com ([10.99.115.17]) by sacrsexc1-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 12 Oct 2010 10:00:01 -0700
Received: from 10.58.61.147 ([10.58.61.147]) by SACMVEXC2-PRD.hq.netapp.com ([10.99.115.16]) with Microsoft Exchange Server HTTP-DAV ; Tue, 12 Oct 2010 16:59:59 +0000
Received: from heimdal.trondhjem.org by SACMVEXC2-PRD.hq.netapp.com; 12 Oct 2010 12:59:59 -0400
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Fred Isaman <iisaman@citi.umich.edu>
In-Reply-To: <AANLkTinx1ZQWko8D9XgmikaGAv4nHxoWJ2bDuM5O=y_u@mail.gmail.com>
References: <AANLkTinx1ZQWko8D9XgmikaGAv4nHxoWJ2bDuM5O=y_u@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Organization: NetApp
Date: Tue, 12 Oct 2010 12:59:58 -0400
Message-ID: <1286902798.24878.9.camel@heimdal.trondhjem.org>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 (2.30.3-1.fc13)
X-OriginalArrivalTime: 12 Oct 2010 17:00:01.0696 (UTC) FILETIME=[E8CCB200:01CB6A2E]
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] question on bulk recall text
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nfsv4>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2010 16:59:11 -0000

On Tue, 2010-10-12 at 12:19 -0400, Fred Isaman wrote:
> The text for bulk recalls in 12.5.5.2.1.5 seems flawed:
> 
>    Once a CB_LAYOUTRECALL of LAYOUTRECALL4_ALL is sent, the server MUST
>    NOT allow the client to use any layout stateid except for
>    LAYOUTCOMMIT operations.  Once the client receives a CB_LAYOUTRECALL
>    of LAYOUTRECALL4_ALL, it MUST NOT use any layout stateid except for
>    LAYOUTCOMMIT operations.
> 
> (similarly for LAYOUTRECALL4_FSID)
> 
> My question: what stateid does the client use to send the required LAYOUTRETURN?

LAYOUTRETURN with a LAYOUTRETURN4_FSID or a LAYOUTRETURN4_ALL argument
doesn't take a stateid. 

Cheers
  Trond

v2.23.0 | Report a Bug | By Email