Re: [nfsv4] possible minor corrections of federated-fs-admin-05

Chuck Lever <chuck.lever@oracle.com> Thu, 23 September 2010 20:04 UTC

Return-Path: <chuck.lever@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 4296A3A6A5F for <nfsv4@core3.amsl.com>; Thu, 23 Sep 2010 13:04:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.319
X-Spam-Level:
X-Spam-Status: No, score=-3.319 tagged_above=-999 required=5 tests=[AWL=-3.278, BAYES_00=-2.599, FB_REPLIC_CAP=6.557, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
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 ZyzElDOv2mDV for <nfsv4@core3.amsl.com>; Thu, 23 Sep 2010 13:04:17 -0700 (PDT)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id 3E5073A659A for <nfsv4@ietf.org>; Thu, 23 Sep 2010 13:04:17 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id o8NK4bgG025183 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 23 Sep 2010 20:04:40 GMT
Received: from acsmt355.oracle.com (acsmt355.oracle.com [141.146.40.155]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o8NK1sip005720; Thu, 23 Sep 2010 20:04:37 GMT
Received: from abhmt019.oracle.com by acsmt354.oracle.com with ESMTP id 631532571285267553; Thu, 23 Sep 2010 11:45:53 -0700
Received: from dhcp-adc-twvpn-1-vpnpool-10-154-24-98.vpn.oracle.com (/10.154.24.98) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 23 Sep 2010 11:45:51 -0700
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Chuck Lever <chuck.lever@oracle.com>
In-Reply-To: <alpine.LFD.2.00.1009230935110.21841@jlentini-linux.nane.netapp.com>
Date: Thu, 23 Sep 2010 14:45:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D661DECC-FF90-47F7-B880-6104D98DCA27@oracle.com>
References: <18218677-5DBE-4ABB-9FF9-E737AC458533@oracle.com> <alpine.LFD.2.00.1009230935110.21841@jlentini-linux.nane.netapp.com>
To: James Lentini <jlentini@netapp.com>
X-Mailer: Apple Mail (2.1081)
Cc: NFSv4 Working Group <nfsv4@ietf.org>
Subject: Re: [nfsv4] possible minor corrections of federated-fs-admin-05
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: Thu, 23 Sep 2010 20:04:18 -0000

On Sep 23, 2010, at 10:06 AM, James Lentini wrote:

> 
> 
> On Wed, 22 Sep 2010, Chuck Lever wrote:
> 
>> Hi James-
>> 
>> The last paragraph of Chapter 5 section 3 says:
>> 
>>> If the junction is resolved, the fileserver will indicate the type of resolution that was performed using the FedFsResolveRes's resolve value and include a list of UUIDs for the FSN's FSLs in the FedFsResolveRes's fslUuid array.
>> 
>> 
>> I think that language needs to be updated to reflect what is now 
>> returned in the result of FEDFS_LOOKUP_JUNCTION.  Most important is 
>> that an array of FedFsFsl structures is returned, not an array of 
>> fslUuids.  I don't recall seeing this change in the most recent set 
>> of diffs, but my memory could be foggy.
> 
> Good catch. I will correct that.
> 
>> Also, we had previously discussed adding a unique error code to the 
>> protocol for "procedure not implemented".  Can that be added in the 
>> next draft update?
> 
> Yes, I can add a FEDFS_ERR_NOTSUPP.
> 
> At the start of Section 5, the specification requires fileservers with 
> junctions (internal nodes) to implement all of the procedures. The 
> procedures are only optional for fileservers that don't support 
> junctions (leaf nodes), so only leaf nodes would be allowed to return 
> FEDFS_ERR_NOTSUPP.

What about CREATE_REPLICATION and friends?

Can FEDFS_LOOKUP_JUNCTION return NOTSUPP for certain resolveTypes?

> Which procedures should be allowed to return FEDFS_ERR_NOTSUPP? All of 
> the procedures except FEDFS_NULL?

-- 
chuck[dot]lever[at]oracle[dot]com