IETF Logo Mail Archive

Re: [nfsv4] [FedFS] Meeting Minutes, 9/30/2010

James Lentini <jlentini@netapp.com> Fri, 01 October 2010 13:50 UTC

Return-Path: <jlentini@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 DEDFD3A6F18 for <nfsv4@core3.amsl.com>; Fri, 1 Oct 2010 06:50:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.779
X-Spam-Level:
X-Spam-Status: No, score=-5.779 tagged_above=-999 required=5 tests=[AWL=0.820, 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 CyJbtNDSch4o for <nfsv4@core3.amsl.com>; Fri, 1 Oct 2010 06:50:01 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by core3.amsl.com (Postfix) with ESMTP id 81FF23A6EE1 for <nfsv4@ietf.org>; Fri, 1 Oct 2010 06:50:01 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.57,266,1283756400"; d="scan'208";a="461344281"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 01 Oct 2010 06:50:50 -0700
Received: from jlentini-linux.hq.netapp.com (jlentini-linux.hq.netapp.com [10.97.16.21]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id o91DompB010531; Fri, 1 Oct 2010 06:50:49 -0700 (PDT)
Date: Fri, 01 Oct 2010 09:50:48 -0400
From: James Lentini <jlentini@netapp.com>
X-X-Sender: jlentini@jlentini-linux.nane.netapp.com
To: Trond Myklebust <trond.myklebust@fys.uio.no>
In-Reply-To: <1285882671.14635.66.camel@heimdal.trondhjem.org>
Message-ID: <alpine.LFD.2.00.1010010939160.21841@jlentini-linux.nane.netapp.com>
References: <alpine.LFD.2.00.1009301550320.21841@jlentini-linux.nane.netapp.com> <34850520-8277-4795-9B5D-573D7907B424@oracle.com> <alpine.LFD.2.00.1009301714310.21841@jlentini-linux.nane.netapp.com> <1285882671.14635.66.camel@heimdal.trondhjem.org>
User-Agent: Alpine 2.00 (LFD 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] [FedFS] Meeting Minutes, 9/30/2010
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, 01 Oct 2010 13:50:03 -0000

On Thu, 30 Sep 2010, Trond Myklebust wrote:

> On Thu, 2010-09-30 at 17:33 -0400, James Lentini wrote:
> > 
> > On Thu, 30 Sep 2010, Chuck Lever wrote:
> > > Some convention for the NFS server's reply in this case should be 
> > > agreed upon outside of the ongoing FedFS discussion.
> > 
> > I think another way to phrase this question is: How does an NFS server 
> > indicate that a file system has moved to an unknown location? One 
> > obvious possibility is to return a zero element locations array in the 
> > fs_locations structure.
> 
> NFS4ERR_STALE is the usual response. If you don't know where the 
> filesystem was migrated to, then what you have is not a migration 
> event. It is an unexport of the partition.

Suppose the server waits to resolve the junction until a GETATTR that 
includes fs_locations[_info]. If the server has already responded with 
an NFS4ERR_MOVED, will an NFS4ERR_STALE return for the GETATTR be a 
reasonable response to the client?

v2.23.0 | Report a Bug | By Email