Re: [nfsv4] Review of 3530bis "Multi-Server Namespace" Chapter

Robert Thurlow <Robert.Thurlow@oracle.com> Fri, 22 October 2010 12:00 UTC

Return-Path: <Robert.Thurlow@oracle.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 9453C3A691A for <nfsv4@core3.amsl.com>; Fri, 22 Oct 2010 05:00:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 1OrzZ+vzhn3J for <nfsv4@core3.amsl.com>; Fri, 22 Oct 2010 05:00:23 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 6DAB83A6915 for <nfsv4@ietf.org>; Fri, 22 Oct 2010 05:00:22 -0700 (PDT)
Received: from rcsinet13.oracle.com (rcsinet13.oracle.com [148.87.113.125]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id o9MC1wAq022934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 22 Oct 2010 12:01:59 GMT
Received: from acsmt355.oracle.com (acsmt355.oracle.com [141.146.40.155]) by rcsinet13.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o9MBjAvM025474; Fri, 22 Oct 2010 12:01:57 GMT
Received: from abhmt002.oracle.com by acsmt355.oracle.com with ESMTP id 706813411287747021; Fri, 22 Oct 2010 04:30:21 -0700
Received: from [10.7.250.62] (/10.7.250.62) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 22 Oct 2010 04:30:21 -0700
Message-ID: <4CC17574.3020503@oracle.com>
Date: Fri, 22 Oct 2010 05:28:52 -0600
From: Robert Thurlow <Robert.Thurlow@oracle.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080811)
MIME-Version: 1.0
To: James Lentini <jlentini@netapp.com>
References: <alpine.LFD.2.00.1009221101060.21841@jlentini-linux.nane.netapp.com> <9F6B463A-0CA8-4C34-A7C2-0BF108745B94@netapp.com> <alpine.LFD.2.00.1010211446060.4707@jlentini-linux.nane.netapp.com>
In-Reply-To: <alpine.LFD.2.00.1010211446060.4707@jlentini-linux.nane.netapp.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] Review of 3530bis "Multi-Server Namespace" Chapter
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: Fri, 22 Oct 2010 12:00:24 -0000

James Lentini wrote:

> <snip>
>>       For the write-verifier class in Section 7.7.7, Section 7.9.1
>>       recommends assuming file system instances are of a different
>>       class in the case of a failover. Is there a recommendation for 
>>       the NFS4ERR_MOVED case? I realize that the recommendations in 
>             ^^^^^^^^^^^^^
>             referral
> 
> 
> To clarify my question: Is there a recommendation for the 
> write-verifier class in the referral case?

I believe the correct answer is that this can't apply to a
referral, since you are creating a relationship with a
filesystem you have not seen (recently, at least).  So I
will add to the violent agreement seen in the rest of the
thread ;-)

Rob T