IETF Logo Mail Archive

Re: [nfsv4] [FedFS] Multiple FSL resolution

Nicolas Williams <Nicolas.Williams@sun.com> Mon, 14 December 2009 18:29 UTC

Return-Path: <Nicolas.Williams@sun.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 67A263A68BE for <nfsv4@core3.amsl.com>; Mon, 14 Dec 2009 10:29:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.915
X-Spam-Level:
X-Spam-Status: No, score=-5.915 tagged_above=-999 required=5 tests=[AWL=0.131, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 YfhrtnloTh9O for <nfsv4@core3.amsl.com>; Mon, 14 Dec 2009 10:29:26 -0800 (PST)
Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43]) by core3.amsl.com (Postfix) with ESMTP id 9F1BF3A68DB for <nfsv4@ietf.org>; Mon, 14 Dec 2009 10:29:26 -0800 (PST)
Received: from dm-central-02.central.sun.com ([129.147.62.5]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id nBEITDj1007507 for <nfsv4@ietf.org>; Mon, 14 Dec 2009 18:29:13 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-02.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL, v2.2) with ESMTP id nBEITDSf053002 for <nfsv4@ietf.org>; Mon, 14 Dec 2009 11:29:13 -0700 (MST)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id nBEIEDY0004340; Mon, 14 Dec 2009 12:14:13 -0600 (CST)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id nBEIEC9j004339; Mon, 14 Dec 2009 12:14:12 -0600 (CST)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Mon, 14 Dec 2009 12:14:12 -0600
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: "Everhart, Craig" <Craig.Everhart@netapp.com>
Message-ID: <20091214181412.GM1516@Sun.COM>
References: <0F3F903BA6B4A54984787888AF6EA5C404671F46@CORPUSMX40A.corp.emc.com> <E7372E66F45B51429E249BF556CEFFBC0961A3AD@RTPMVEXC1-PRD.hq.netapp.com> <20091214164337.GK1516@Sun.COM> <E7372E66F45B51429E249BF556CEFFBC096D5C46@RTPMVEXC1-PRD.hq.netapp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <E7372E66F45B51429E249BF556CEFFBC096D5C46@RTPMVEXC1-PRD.hq.netapp.com>
User-Agent: Mutt/1.5.7i
Cc: nfsv4@ietf.org, stacey_chris@emc.com
Subject: Re: [nfsv4] [FedFS] Multiple FSL resolution
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, 14 Dec 2009 18:29:27 -0000

On Mon, Dec 14, 2009 at 12:49:08PM -0500, Everhart, Craig wrote:
> Nico, what do you mean "resolving" a junction?  I'd expect that the
> server consults the listed NSDB, looks up the entry for the FSN, gets
> the list of FSLs, and passes some/most/all of them to the FS client.

I mean exactly that: the process of obtaining a list of nfs4_locations
to return to the client.

> The file server shouldn't have to further resolve the FSLs, nor should
> it have to consult more than one NSDB for the list of FSLs.  Would this
> be incorrect?

Right.

Nico
--

v2.23.0 | Report a Bug | By Email