Re: [nfsv4] State of NFSv4 implementations ( who is active )

Rick Macklem <rmacklem@uoguelph.ca> Mon, 28 October 2019 16:59 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 299231200F5 for <nfsv4@ietfa.amsl.com>; Mon, 28 Oct 2019 09:59:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 oOavIu9PwKyL for <nfsv4@ietfa.amsl.com>; Mon, 28 Oct 2019 09:59:05 -0700 (PDT)
Received: from CAN01-QB1-obe.outbound.protection.outlook.com (mail-eopbgr660044.outbound.protection.outlook.com [40.107.66.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB5AD12008B for <nfsv4@ietf.org>; Mon, 28 Oct 2019 09:59:04 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=YD3w28f4MsWve9EobIwUsffJSg2po/5F5l9HuAeytPHz4VVefymJd1nVFEVmWbtPK0j4msldyPlhybnV4S65kWTQc8lP/HhKAkjom91sQLzk9nBgaZlb/Enl+J2iH+8B3sKLWU2rw4br53tlyLGNHbsbYBKqF5bj5QAbk8DUMfmJGhfVkncwfLHpuGhAO+FXSqjL7XvCDN54XlCQXYot2ZLdpew27l/IHxhge7dRHgZoKJ/R4snDkgn3lepFUF3AG/O9RhITUQO36L5V5ZMqsjJVz28iZo5DzgvzXrMcK3qTkCGD5y8Pkc04BI7lJbKatJ4CW/rzEXYRAopGQwhubA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=YBoPpRK1S7lmKd8uV4Z3kDpof4NuwK0CGR6F9UsP6VI=; b=KFn1PoYvCSj4A0zcAQADbvyuih2GyOxgFGp5ut+xVnZGpRKMh4XywtwxXad89PXSe+TjfgTroFvgLEz9aPYK93YKy5GKbQbqndfSP6aZG/WNWFvyvPK4eSzmZx1jvvqFQeIgKT62MpU/qrOYzekXO6Zn6oagvrgbzSAMcthZPxGSfVBco41nwQoEOZNcJR4xiXDw171r78obL8pOH7Ls2iYIZwcgQjBHWCPfGJRqXltkr63xyHxxPD1w9fXozvJ5Z0yhBqVrvQRdP0/EjRcEnZLDUg9VsgfqxHaS/jXP7tFPwqvMEEU+ug63EPSDzS8Oixas70iY6tGlcaGtOnhFFw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=uoguelph.ca; dmarc=pass action=none header.from=uoguelph.ca; dkim=pass header.d=uoguelph.ca; arc=none
Received: from YTBPR01MB2845.CANPRD01.PROD.OUTLOOK.COM (10.255.13.156) by YTBPR01MB3103.CANPRD01.PROD.OUTLOOK.COM (10.255.47.212) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2387.24; Mon, 28 Oct 2019 16:59:03 +0000
Received: from YTBPR01MB2845.CANPRD01.PROD.OUTLOOK.COM ([fe80::45c3:a411:3ee8:a12e]) by YTBPR01MB2845.CANPRD01.PROD.OUTLOOK.COM ([fe80::45c3:a411:3ee8:a12e%5]) with mapi id 15.20.2387.023; Mon, 28 Oct 2019 16:59:03 +0000
From: Rick Macklem <rmacklem@uoguelph.ca>
To: Chuck Lever <chuck.lever@oracle.com>, spencer shepler <spencer.shepler@gmail.com>
CC: NFSv4 <nfsv4@ietf.org>
Thread-Topic: [nfsv4] State of NFSv4 implementations ( who is active )
Thread-Index: AQHVjVVBwCn8POtAAEeEIKhTl69v46dwKMKAgAAYL8U=
Date: Mon, 28 Oct 2019 16:59:02 +0000
Message-ID: <YTBPR01MB2845EBE9C268BEE742386ADDDD660@YTBPR01MB2845.CANPRD01.PROD.OUTLOOK.COM>
References: <CAFt6Bammns-K5Mb6LFiQ9yXyAWFe7b_YKdDWzcNbvwN5GPRHaw@mail.gmail.com>, <CA1F137C-1B7B-4B46-A960-88F93A614B9A@oracle.com>
In-Reply-To: <CA1F137C-1B7B-4B46-A960-88F93A614B9A@oracle.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca;
x-originating-ip: [2001:569:fac0:e900:9131:b734:ba09:18ee]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ebd70a76-f0b1-458d-a628-08d75bc822c0
x-ms-traffictypediagnostic: YTBPR01MB3103:
x-microsoft-antispam-prvs: <YTBPR01MB3103D4CF822CC33EB7C06435DD660@YTBPR01MB3103.CANPRD01.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 0204F0BDE2
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(376002)(136003)(39860400002)(396003)(366004)(199004)(55674003)(189003)(71190400001)(86362001)(8676002)(486006)(186003)(229853002)(76176011)(7696005)(33656002)(71200400001)(8936002)(6506007)(81156014)(6116002)(81166006)(6436002)(102836004)(99286004)(74316002)(46003)(6246003)(316002)(786003)(305945005)(7736002)(110136005)(64756008)(25786009)(66556008)(76116006)(14454004)(66446008)(66476007)(5660300002)(91956017)(66946007)(52536014)(2906002)(478600001)(446003)(14444005)(256004)(55016002)(11346002)(4326008)(476003)(9686003); DIR:OUT; SFP:1101; SCL:1; SRVR:YTBPR01MB3103; H:YTBPR01MB2845.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: HN8HKw6pvHcpk9fKRgGGIr4/0bNzsaUq/MPRh8RP1nbe4MrCow07Cawb/QDFd93H2s7Ag+hyTPLc9AjRKXHcrX7eoL8xJLRW/B7XFwIEpMLM4eSgS3e/+BNyPdEVZ6iW+RYUD+3JvyNZ2mxy5SF56gJffxxj1lhZjKWhqe/Gsbpb5EM8AYEOcUQIaTmLBdIOX1MkmD6PvbTbrjEEpBFKYFCluJ/fJF6GiqWh+vHKFkjvG5wrPapcSn0viAhCV/5z1nfhheRO4slufVV9lWmCsJu0t473QS+I8AXQ1QbW9IpNzX6wJ+pJJ2VnXlQetlXtfH8pi8z2E9q5tx+he8/y6hNaZBCEmzuPRMsF+7iu85fJ7uZ5ma3zaYlrq/CnjlZJ6dhlanfj2aY6jJNx5btD5gxByj7RzwaiGzl3X023gynmfBj8RuXpPTrx8eDFau/w
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: uoguelph.ca
X-MS-Exchange-CrossTenant-Network-Message-Id: ebd70a76-f0b1-458d-a628-08d75bc822c0
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Oct 2019 16:59:02.9512 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Rb8EMNXzxD5i/oV4W3ZNONHY8VX1ZjEV85qp+dEByToBChNqRJuF0hKbY0iPT12fob9+hnTfWziWeYc5S52kRg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTBPR01MB3103
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/EBX3klFgIuOdpP4DrQfMsiT7Y_4>
Subject: Re: [nfsv4] State of NFSv4 implementations ( who is active )
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: Mon, 28 Oct 2019 16:59:07 -0000

Chuck Lever wrote:
[good stuff snipped]
>Not sure if Amazon is on this list, so I will mention that they
>also have an elastic cloud data center NFS server implementation
>known as EFS. It supports NFSv4.x, but I believe that pNFS is not
>supported.
Yes, it would be nice if someone could make contact with them. I posted
here a year or two ago when I had an issue and never got any response.

It works fine with the FreeBSD client, except it has one fairly significant
flaw (that other client implementors might want to know about).
It stores session/open/lock state per cluster (I have no idea what constitutes
a cluster for EFS) and not globally.
As such, when the client establishes a new TCP connection, it sometimes
connects to a different cluster and then the client ends up doing a full
session/open/lock state recovery like it would for a traditional server reboot.
(It exposed a bunch of problems with the FreeBSD client's recovery code,
 so it served as a good debugging tool for the FreeBSD client.)

The other group that would be nice to get more involved (I haven't seen
posts and don't know if they attend Bakeathons?) is the VMware NFSv4.1
(don't know if they are working on NFSV4.2) client.
The first release (ESXi 6.5) had serious issues, but most of these were fixed
for ESXi 6.7, from what I saw. I never made contact with the group, but
someone who worked elsewhere within VMware posted my list of
problems on their internal bug tracker. That seemed to work?

As for FreeBSD:
- NFSv2->4.1 client and server released. Support for File and Flexible File
   layouts for pNFS for client and server. (No striping support in the server
   or Flexible File client code.)
   No support for RDMA or migration.
- NFSv4.2 client/server code nearing completion. Should be released in
   FreeBSD13 (and maybe FreeBSD12.2). Figure 6months->1year from now.
   - Available for testing in the meantime.
  Includes: intra-server copy, allocate, seek, advise (WILLNEED/DONTNEED),
     layouterror. It also has RFC-8276 xattr in it.
   Might have some MAC label support, but I haven't coded that yet.
Only RPCSEC_GSS_V1 at this time (part of the reason I am hesitant w.r.t. MAC
labelling).

rick (Hi Spencer:-)