Re: [nfsv4] "Courtesy locks"

Rick Macklem <rmacklem@uoguelph.ca> Mon, 13 September 2010 23:38 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 DD68C3A6846 for <nfsv4@core3.amsl.com>; Mon, 13 Sep 2010 16:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.142
X-Spam-Level:
X-Spam-Status: No, score=-6.142 tagged_above=-999 required=5 tests=[AWL=0.457, 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 YN8e84mN8B+j for <nfsv4@core3.amsl.com>; Mon, 13 Sep 2010 16:38:18 -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 C0F6F3A681D for <nfsv4@ietf.org>; Mon, 13 Sep 2010 16:38:12 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApwEAHpSjkyDaFvO/2dsb2JhbACDG58hs12SDYEigyp0BIon
X-IronPort-AV: E=Sophos;i="4.56,361,1280721600"; d="scan'208";a="93748777"
Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 13 Sep 2010 19:38:38 -0400
Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 08C1EB3F31; Mon, 13 Sep 2010 19:38:38 -0400 (EDT)
Date: Mon, 13 Sep 2010 19:38:38 -0400
From: Rick Macklem <rmacklem@uoguelph.ca>
To: Mike Mackovitch <macko@apple.com>
Message-ID: <1463622341.860473.1284421117976.JavaMail.root@erie.cs.uoguelph.ca>
In-Reply-To: <20100913160643.GA45938@wacko.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [24.65.230.102]
X-Mailer: Zimbra 6.0.7_GA_2476.RHEL4 (ZimbraWebClient - SAF3 (Mac)/6.0.7_GA_2473.RHEL4_64)
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] "Courtesy locks"
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: Mon, 13 Sep 2010 23:38:24 -0000

> 
> For the Mac OS X NFSv4 client:
> 
> > C1) When you get NFS4ERR_EXPIRED, what happens?
> >
> >     a) Assume all locks associated with lease have been released
> >        that the client needs to create a new clientid?
> >     b) Assume that it means one or more locks have been lost and
> >        the client needs to determine what as gone and which are
> >        still valid.
> 
> (b)
> 
> Upon receipt of NFS4ERR_EXPIRED the client will enter recovery mode
> where we will attempt to reclaim all opens, all locks and delegated
> state (if we didn't have non-delegated state that already covered it)
> and drop/return any lingering delegations we had.

The FreeBSD8 server will only allow reclaim Ops during the grace
period right after a reboot. It will return NFS4ERR_NO_GRACE for
all reclaim Ops (Open with Claim_previous or Lock with the reclaim
flag true) received outside of this grace period.

Do other servers allow this? (I thought the above was required
behaviour?)

[good stuff snipped for brevity]

rick