Re: State of NFSv4 implementations ( who is active )

"van der Linden, Frank" <[email protected]> Mon, 28 Oct 2019 17:06:50 +0000

Newsgroups	gmane.ietf.nfsv4
Message-ID	<[email protected]>

I know that team - let me forward your mail to them. I don't believe they are on this list.

Frank

On 10/28/19, 10:00 AM, "nfsv4 on behalf of Rick Macklem" <[email protected] on behalf of [email protected]> wrote:

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:-)

_______________________________________________
nfsv4 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nfsv4