From owner-freebsd-fs@FreeBSD.ORG Mon Jun 2 13:24:23 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 86686EB6 for ; Mon, 2 Jun 2014 13:24:23 +0000 (UTC) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id DEE82248C for ; Mon, 2 Jun 2014 13:24:21 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqAEANxejFODaFve/2dsb2JhbABYhDGCbL9ngSd0gk+BCwINGQJfiFWgYY8ipDsXgSqMdIMwgUsErS2DVCGBcg X-IronPort-AV: E=Sophos;i="4.98,957,1392181200"; d="scan'208";a="125564179" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-annu.net.uoguelph.ca with ESMTP; 02 Jun 2014 09:23:11 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 9C7B6B4033 for ; Mon, 2 Jun 2014 09:23:11 -0400 (EDT) Date: Mon, 2 Jun 2014 09:23:11 -0400 (EDT) From: Rick Macklem To: FreeBSD Filesystems Message-ID: <220107037.9988770.1401715391557.JavaMail.root@uoguelph.ca> Subject: RFC and testing: NFSv4.1 server going into head MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jun 2014 13:24:23 -0000 Hi, I think that the NFSv4.1 server code in projects/nfsv4.1-server is about ready to be merged into head. As such, if anyone has the resources to do so in the next 2 weeks, please take a look at the code and/or test it. Also, feel free to make any comments w.r.t. merging this code into head, such as preferred timing, whether or not you think it should happen, etc. If/when the merge is done, it will be fairly large, but shouldn't affect the NFSv3, NFSv4.0 server functionality (however, I may screw up and break them for a little while;-). I think NFSv4.1 might be useful, since it uses sessions to provide "exactly once" RPC semantics, which should improve overall correctness. This server code does not have any pNFS support in it. Implementing a pNFS server is a large project that may happen someday. Thanks in advance for any testing/review/comments, rick ps: The NFSv4.1 client is already in head and the options for mounting with NFSv4.1 are "nfsv4.minorversion=1" for FreeBSD and "vers=4,minorversion=1" for the Linux client.