Re: [nfsv4] Possible change to Flex Files layout
Rick Macklem <rmacklem@uoguelph.ca> Thu, 10 March 2016 04:20 UTC
Return-Path: <rmacklem@uoguelph.ca>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97B6712DC12 for <nfsv4@ietfa.amsl.com>; Wed, 9 Mar 2016 20:20:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level:
X-Spam-Status: No, score=-4.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id enGgIuRri2oL for <nfsv4@ietfa.amsl.com>; Wed, 9 Mar 2016 20:20:19 -0800 (PST)
Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5A3E512D73B for <nfsv4@ietf.org>; Wed, 9 Mar 2016 20:20:19 -0800 (PST)
IronPort-PHdr: 9a23:chJBAxYZavQs2mDw8zseni3/LSx+4OfEezUN459isYplN5qZpcu8bnLW6fgltlLVR4KTs6sC0LqJ9fC/EjNZqb+681k8M7V0HycfjssXmwFySOWkMmbcaMDQUiohAc5ZX0Vk9XzoeWJcGcL5ekGA6ibqtW1aJBzzOEJPK/jvHcaK1oLsh7/0q8KYPFwArQH+SI0xBS3+lR/WuMgSjNkqAYcK4TyNnEF1ff9Lz3hjP1OZkkW0zM6x+Jl+73YY4Kp5pIZoGJ/3dKUgTLFeEC9ucyVsvJWq5lH/Sl6z/HwaXi0zgxlMDgLY9w2yCovrtS32s/tV1yyTPMmwRrcxD2eM9aBuHSXpgyRPEjcy82Xaj4QklqdSqxGlqhlX3onbfYyRLPo4daqLLoBSfnZIQssED38JOYi7dYZaSrNZZes=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2DPAQDX9OBW/61jaINehA1tBrpRAQ2BbSGFbgKBehQBAQEBAQEBAWMngi2CFAEBAQMBI1YFCwIBCBgCAg0ZAgJXAgQTiBwIDrAKjyUBAQEBAQEBAwEBAQEBAQEVBHyFHIF7gkeEIoMYgToFjiaJEoVliXKHa4UujlwCHgEBQoQCHi4BiFR+AQEB
X-IronPort-AV: E=Sophos;i="5.24,314,1454994000"; d="scan'208";a="270133383"
Received: from nipigon.cs.uoguelph.ca (HELO zcs1.mail.uoguelph.ca) ([131.104.99.173]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 09 Mar 2016 23:20:18 -0500
Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 2F07215F574; Wed, 9 Mar 2016 23:20:18 -0500 (EST)
Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id kZPsrhfyAEii; Wed, 9 Mar 2016 23:20:17 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 4BB0715F577; Wed, 9 Mar 2016 23:20:17 -0500 (EST)
X-Virus-Scanned: amavisd-new at zcs1.mail.uoguelph.ca
Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 3osf-K_sOPQC; Wed, 9 Mar 2016 23:20:17 -0500 (EST)
Received: from zcs1.mail.uoguelph.ca (zcs1.mail.uoguelph.ca [172.17.95.18]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 2127C15F574; Wed, 9 Mar 2016 23:20:17 -0500 (EST)
Date: Wed, 09 Mar 2016 23:20:17 -0500
From: Rick Macklem <rmacklem@uoguelph.ca>
To: Trond Myklebust <trondmy@gmail.com>
Message-ID: <719941678.11954491.1457583617111.JavaMail.zimbra@uoguelph.ca>
In-Reply-To: <CAABAsM7hN_FSC7VUCvjOpCoJvii0PK7LvJjFy1u_dRiDtzxNZQ@mail.gmail.com>
References: <1244659329.10251491.1457494754382.JavaMail.zimbra@uoguelph.ca> <CAABAsM7hN_FSC7VUCvjOpCoJvii0PK7LvJjFy1u_dRiDtzxNZQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.17.95.12]
X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - FF44 (Win)/8.0.9_GA_6191)
Thread-Topic: Possible change to Flex Files layout
Thread-Index: wKyfn3PH1x9ijFansjqJE091yPil2Q==
Archived-At: <http://mailarchive.ietf.org/arch/msg/nfsv4/1jB0Q0QmxmF5RAkqRDKTABsezYo>
Cc: nfsv4 <nfsv4@ietf.org>
Subject: Re: [nfsv4] Possible change to Flex Files layout
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 10 Mar 2016 04:20:21 -0000
Trond Myklebust wrote: > Hi Rick, > > On Tue, Mar 8, 2016 at 10:39 PM, Rick Macklem <rmacklem@uoguelph.ca> wrote: > > Hi, > > > > I am building an NFSv4.1 pNFS for FreeBSD using Flex Files and > > I've run into a case where it would be nice to make a small > > addition to the layout. > > > > I have a case where the files are replicated over K of the N > > servers in the cluster. Which K of the N is on a per file basis. > > (I am using GlusterFS as a backend and this is its replication > > strategy, if I understand it correctly.) > > > > When there are replicas, the files are basically mirrored, but > > writes only need to be done to one of the replicas/mirrors. > > (Again, if I understand what GlusterFS does.) > > > > -- So, what do others think of adding a boolean for the layout > > that says "only one mirror needs to be written VS all mirrors > > need to be written". > > > > I can live without this, but I think I would find it useful and > > I don't see a problem with adding it. > > > > Thanks for your consideration of this, rick > > I don't see any major problems with this request. We have the > ffl_flags field in the layout, and so adding a flag for this would be > trivial, and could be done without breaking existing clients. Those > existing implementations would presumably be inefficient, since they > would ignore the flag, and continue to write to all mirrors, but they > would not break. > > One question I have, though, is how this would affect the > ffds_efficiency? The current expectation for that field is that it > applies only to the mirrored read case, where you want to select one > of many mirrors. Wouldn't we also want to extend that scope of that > field so that it can apply to writes? > Either way I think we'd need a proposal for how we might modify the > description in > https://tools.ietf.org/html/draft-ietf-nfsv4-flex-files-06#section-8.1 > More re propagation of a write to the mirrors: Obviously, without a "write one mirror" flag, the client knows when all mirrors are written, since the client does it. In the "diff" I posted a few minutes ago... - It stated that the write would be propagated to the mirrors before the write reply was sent. - The "softer" version of this would be to require the write to be propagated to all mirrors by the time the Commit reply is sent to the client. The "softer" version may be preferable, since it doesn't put as strong a requirement on the server, but still allows the client to ensure the write is propagated by doing a Commit when necessary. If both seem appropriate, an additional FF_FLAGS_xx could be introduced to indicate to the client which of the above the server provides when FF_FLAGS_WRITE_ONE_MIRROR is set. So, what do others think w.r.t. this? Thanks, rick > Cheers > Trond >
- [nfsv4] Possible change to Flex Files layout Rick Macklem
- Re: [nfsv4] Possible change to Flex Files layout Trond Myklebust
- Re: [nfsv4] Possible change to Flex Files layout Rick Macklem
- Re: [nfsv4] Possible change to Flex Files layout Benny Halevy
- Re: [nfsv4] Possible change to Flex Files layout Rick Macklem
- Re: [nfsv4] Possible change to Flex Files layout Benny Halevy
- Re: [nfsv4] Possible change to Flex Files layout Rick Macklem
- Re: [nfsv4] Possible change to Flex Files layout Benny Halevy
- Re: [nfsv4] Possible change to Flex Files layout David Noveck
- Re: [nfsv4] Possible change to Flex Files layout Matt Benjamin
- Re: [nfsv4] Possible change to Flex Files layout Rick Macklem
- Re: [nfsv4] Possible change to Flex Files layout Rick Macklem
- Re: [nfsv4] Possible change to Flex Files layout Benny Halevy
- Re: [nfsv4] Possible change to Flex Files layout Rick Macklem
- Re: [nfsv4] Possible change to Flex Files layout Trond Myklebust
- Re: [nfsv4] Possible change to Flex Files layout Thomas Haynes
- Re: [nfsv4] Possible change to Flex Files layout David Noveck
- Re: [nfsv4] Possible change to Flex Files layout Rick Macklem