Re: [nfsv4] Extended Attributes NFSv4

David Noveck <davenoveck@gmail.com> Fri, 02 August 2019 16:59 UTC

Return-Path: <davenoveck@gmail.com>
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 72D071206F9 for <nfsv4@ietfa.amsl.com>; Fri, 2 Aug 2019 09:59:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 aMVzRoNovSs0 for <nfsv4@ietfa.amsl.com>; Fri, 2 Aug 2019 09:59:51 -0700 (PDT)
Received: from mail-oi1-x22d.google.com (mail-oi1-x22d.google.com [IPv6:2607:f8b0:4864:20::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8DB91206F6 for <nfsv4@ietf.org>; Fri, 2 Aug 2019 09:59:51 -0700 (PDT)
Received: by mail-oi1-x22d.google.com with SMTP id s184so57326939oie.9 for <nfsv4@ietf.org>; Fri, 02 Aug 2019 09:59:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=NrDMfvgYPQq4XRw0OykOqGFdj+HL3HIVlQVtxCnrol8=; b=CsFWEu8acV+wHij/X4gN3mFeY38PBc+h9WOqnP0oVMygwz9KZbNWuV04yfzYQ3kvQf jTvBhgeW7+PbkxCEv+U1ovbRw+hNONvbEMi+OFo0BQfLaPFqgdgMXrzh2vZEUWcjn3Oa fzT6xaoDfG861ljaiwrPJXMX/dbWpYkLjAFRKY+Vava76XeFb6F1w1xGuar0DH6rA7vi Alhz6D5GhcT8BmY3YyU5ct5OhSpI1sYP+/PQ6vcfsf+v3pGTAmYa/WkHaFbusWK0Hm5a y0N9mn/o9+Zz8wASfergSoiY538vLIB07X6OGi/U1ryJqtlo5dVGMTRtfEVHmpm5lRMK 4MGA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=NrDMfvgYPQq4XRw0OykOqGFdj+HL3HIVlQVtxCnrol8=; b=ehvA0hC8DImD2CDLIhuuPSRZ6vgpooJ2xpOj9TeEY2ZAUdnrqWTIP/0w6OVPIF3vg6 3EjExZ2m4bbuyu5ZkK2BsxgDsQgktdrVngP3T//TplFD3nhiq/jb4jXwzN3xo6D+PKM9 xx8yBHvW5xl5EGgn3zWG1k0RfdLSvRuvRGP5Jnj67DPE7796QNY10Nu445sRDMvnwVIb LIOqTCvViFnmwvzi2GT3lfYKWdNkYwHx8THCkdvSp31OqRa12BfhRaLY+OGTFP1tJskH f141owaDAnfQASZYi6u6tt9OVZgZRxU4EmhVo/2IdWnB5iplvRT4m3gxvOPcV1/xCQ5Z O2cQ==
X-Gm-Message-State: APjAAAWGe6zFSi6oc1a+PZWbh6nlGixvmA/r+Oa0e3Ux8ZxtFV9G9cp7 9nm5TYvDVAGUy8WMRk+gerUGKYGBkpxuOnWiRHw=
X-Google-Smtp-Source: APXvYqyosp1yl/h7MPz0wsRYPDkFMu6QsZIbJPkU428vNCaeBbNdY5vhl63YFGFBOjyLF3+ek6VQko+cjxpHuar9lko=
X-Received: by 2002:aca:b2d5:: with SMTP id b204mr3066439oif.101.1564765190780; Fri, 02 Aug 2019 09:59:50 -0700 (PDT)
MIME-Version: 1.0
References: <CADowLe+VaR15Bw49oNrZWtYLNcG6__kG2oD+yiOS07ON9mKTuQ@mail.gmail.com> <ecac6b1e73df449ea3b86f16c251aaa6@x13pwdurdag1001.AMER.DELL.COM>
In-Reply-To: <ecac6b1e73df449ea3b86f16c251aaa6@x13pwdurdag1001.AMER.DELL.COM>
From: David Noveck <davenoveck@gmail.com>
Date: Fri, 02 Aug 2019 12:59:39 -0400
Message-ID: <CADaq8jesWJQnVtgaPkUSW--PjFj=SCGhfE6FBMabLELE8YDJcg@mail.gmail.com>
To: "faibish, sorin" <Faibish.Sorin@dell.com>
Cc: victor.asencio@upr.edu, Philip.Shilane@dell.com, "Black, David" <David.Black@dell.com>, NFSv4 <nfsv4@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005a7ef4058f2549e0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/gmB-g5PnVD4xy2WKhrCT1ZnEo5k>
Subject: Re: [nfsv4] Extended Attributes NFSv4
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 02 Aug 2019 16:59:55 -0000

> The NFSv4 WG rejected the idea of using extended attributes that were
specified in the rfc 8276.

I don't  think the working group considered and rejected the idea using
extended attributes,   Making a decision like that is way too organized for
an IETF working group, especally given that we had ten minutes to devote to
the topic.

Nevertheless, many members seemed to feel Sorin's attributes were not a
good fit for the xattrs in rfc 8276, and, while I can't speak for the
group, I'd like to explain while I felt that way.

rfc8276 defines a mechanism to provide for user xattrs, i.e. those that are
totally opaque to the server and which the server essentially treats pretty
much as user data.    In many cases we do have items which are system
xattrs in Linux (e.g. IMA metadata).  Thse are typically handled as
ordinary optional attributes.    This works OK since the set of OPTIONAL
attributes can be easily extended, as described in RFC 8178.

> It seems nobody implemented xattr per the rfc.

It appears that implementation has lagged.  I'm not sure why.   In any
case, I don't feel that the decision about whether xattrs should be used
for the data reduction attributes should turn on the pace of
implementationof the xattr feature.

> If you have any plans for that please let the NFSv4 WG know sending this
email to the nfsv4 list I added here.

I certainly would like to know about such plans.   It is hard to invest in
server-side implementations of a feature when there are no client-side
implementations in the horizon.

On Tue, Jul 30, 2019 at 11:47 AM <Faibish.Sorin@dell.com> wrote:

> Victor,
>
>
>
> Just to keep you expectations low, the NFSv4 WG rejected the idea of using
> extended attributes that were specified in the rfc 8276. It seems nobody
> implemented xattr per the rfc. If you have any plans for that please let
> the NFSv4 WG know sending this email to the nfsv4 list I added here. Thanks
>
>
>
> ./Sorin
>
>
>
>
>
> *From:* Victor A Asencio Casiano <victor.asencio@upr.edu>
> *Sent:* Tuesday, July 30, 2019 10:43 AM
> *To:* faibish, sorin; Shilane, Philip; Black, David
> *Cc:* manoj.naik@nutanix.com; eshel@us.ibm.com
> *Subject:* Extended Attributes NFSv4
>
>
>
> [EXTERNAL EMAIL]
>
> Good morning, I’m currently interested in adding extended attributes to
> NFSv4 and I would like if you can send me in the right direction. RFC 8276
> and your draft (Support for Data Reduction Extended Attributes in nfsv4
> Version 2) are the only serious documents that I found about this topic. I
> would like to know if Extended Attributes have been already implemented
> somewhere that I can test it out, or If someone try to implement this
> before or any source code that I can reach out or any draft code? Besides
> the code portions that appears on RFC 8276.
>
>
>
> Thanks for your help.
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4
>