Re: [nfsv4] can a server replace a read deleg with a write deleg?
Rick Macklem <rmacklem@uoguelph.ca> Sun, 04 July 2010 23:37 UTC
Return-Path: <rmacklem@uoguelph.ca>
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 AAEE23A67F3 for <nfsv4@core3.amsl.com>; Sun, 4 Jul 2010 16:37:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.299
X-Spam-Level:
X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=1.300, 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 kXn2KJ0LVKyl for <nfsv4@core3.amsl.com>; Sun, 4 Jul 2010 16:37:04 -0700 (PDT)
Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by core3.amsl.com (Postfix) with ESMTP id A62E23A67F2 for <nfsv4@ietf.org>; Sun, 4 Jul 2010 16:37:04 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAHO4MEyDaFvI/2dsb2JhbACfaXG8BYUlBA
X-IronPort-AV: E=Sophos;i="4.53,537,1272859200"; d="scan'208";a="83008427"
Received: from darling.cs.uoguelph.ca ([131.104.91.200]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 04 Jul 2010 19:36:59 -0400
Received: from localhost (localhost.localdomain [127.0.0.1]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id E4EA3940114; Sun, 4 Jul 2010 19:37:00 -0400 (EDT)
X-Virus-Scanned: amavisd-new at darling.cs.uoguelph.ca
Received: from darling.cs.uoguelph.ca ([127.0.0.1]) by localhost (darling.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VBeTwftbg2Mw; Sun, 4 Jul 2010 19:37:00 -0400 (EDT)
Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id 00F05940020; Sun, 4 Jul 2010 19:36:59 -0400 (EDT)
Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id o64Ns8d02234; Sun, 4 Jul 2010 19:54:08 -0400 (EDT)
X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs
Date: Sun, 04 Jul 2010 19:54:08 -0400
From: Rick Macklem <rmacklem@uoguelph.ca>
X-X-Sender: rmacklem@muncher.cs.uoguelph.ca
To: Trond Myklebust <trond.myklebust@fys.uio.no>
In-Reply-To: <1278260672.29898.13.camel@heimdal.trondhjem.org>
Message-ID: <Pine.GSO.4.63.1007041947180.1654@muncher.cs.uoguelph.ca>
References: <Pine.GSO.4.63.1007041217520.6453@muncher.cs.uoguelph.ca> <1278260672.29898.13.camel@heimdal.trondhjem.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] can a server replace a read deleg with a write deleg?
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: Sun, 04 Jul 2010 23:37:05 -0000
On Sun, 4 Jul 2010, Trond Myklebust wrote: > > I read RFC3530 as being perfectly clear on this. > > In section 9.4 it explicitly states that the client _cannot_ make any > changes to the contents or attributes of the file if it holds a read > delegation. > Ok, here are 2 paras from page 103: When a client has a read open delegation, it may not make any changes to the contents or attributes of the file but it is assured that no other client may do so. When a client has a write open delegation, it may modify the file data since no other client will be accessing the file's data. The client holding a write delegation may only affect file attributes which are intimately connected with the file data: size, time_modify, change. I see this as saying the read open delegation doesn't allow writing to the file, but I don't see it saying "the client can't open the file for writing against the server without first returning the delegation". (Btw, I have no problem with it saying that, I just didn't get that from the above para, especially given what it says in the next para.) When a client has an open delegation, it does not send OPENs or CLOSEs to the server but updates the appropriate status internally. -> For a read open delegation, opens that cannot be handled locally (opens for write or that deny read access) must be sent to the server. I see "->" simply saying that the open has to be done against the server. If the read open delegation must be returned for the open to be done, shouldn't it state that explicitly. > In section 9.4.4 it states that the server must recall the delegation in > the event of a conflicting OPEN or READ/WRITE w/ special stateids. > If the open for writing is from the same client that holds the read open delegation, it didn't hit me as a "conflict". I would have thought a conflicting OPEN would have been one from a different client? Isn't the english language wonderfully ambiguous? If others feel the wording is clear, then I have no problem with it. ie. If the client doesn't return the read open delegation before doing an open for writing against the server, the server will CBRECALL it. rick
- [nfsv4] can a server replace a read deleg with a … Rick Macklem
- Re: [nfsv4] can a server replace a read deleg wit… Trond Myklebust
- Re: [nfsv4] can a server replace a read deleg wit… Rick Macklem
- Re: [nfsv4] can a server replace a read deleg wit… Trond Myklebust
- Re: [nfsv4] can a server replace a read deleg wit… david.noveck
- Re: [nfsv4] can a server replace a read deleg wit… david.noveck
- Re: [nfsv4] can a server replace a read deleg wit… Rick Macklem