From owner-freebsd-stable@FreeBSD.ORG Thu May 21 01:57:52 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BFBB12BC for ; Thu, 21 May 2015 01:57:52 +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 9E0401796 for ; Thu, 21 May 2015 01:57:51 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2CxAwCeOl1V/95baINcg2ReBoMYwD4JgVAKhS1KAoF1FAEBAQEBAQGBCoQiAQEBAwEBAQEgKyALBRYYAgINGQIpAQkmBggCBQQBHASIAwgNqzCkBQEBAQEGAQEBAQEBARuBIYoZhCwHAQEFFzQHgmiBRQWXIYQag1w+hiuEe4oJI4Fmgi4iMQd8CRcjgQEBAQE X-IronPort-AV: E=Sophos;i="5.13,466,1427774400"; d="scan'208";a="213626450" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-annu.net.uoguelph.ca with ESMTP; 20 May 2015 21:57:45 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 6E80BB3F85; Wed, 20 May 2015 21:57:43 -0400 (EDT) Date: Wed, 20 May 2015 21:57:43 -0400 (EDT) From: Rick Macklem To: Mahmoud Al-Qudsi Cc: freebsd-stable@freebsd.org Message-ID: <1013279983.41809469.1432173463439.JavaMail.root@uoguelph.ca> In-Reply-To: <44D62B59-1ABE-4FC3-9E29-39478A94703E@neosmart.net> Subject: Re: Status of NFS4.1 FS_RECLAIM in FreeBSD 10.1? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.10] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2015 01:57:52 -0000 Mahoud Al-Qudsi wrote: > Hello, > > I have not delved too deeply into either the NFS spec or the FreeBSD > nfsd > code, but from my admittedly-limited understanding, it seems that > reclaim is > both a mandatory feature and one that is present in the current > FreeBSD NFS > v4.1 implementation. Is my understanding of this correct? > Only the global RECLAIM_COMPLETE is implemented. I'll be honest that I don't even really understand what the "single fs reclaim_complete" semantics are and, as such, it isn't implemented. I think it is meant to be used when a file system is migrated from one server to another (transferring the locks to the new server) or something like that. Migration/replication isn't supported. Maybe someday if I figure out what the RFC expects the server to do for this case. > My reason for asking is when attempting to migrate an ESXi server to > a FreeBSD > NFSv4.1 datastore, ESXi throws the following error: > > > WARNING: NFS41: NFS41FSCompleteMount:3601: RECLAIM_COMPLETE FS > > failed: Not > > supported; forcing read-only operation > This is the first time I've heard of a client using this. The only clients I've ever had the opportunity to test against are Linux, Solaris and the FreeBSD one. > VMware ESXi 6.0 is able to mount NFSv4.1 shares exported from other > operating systems, so I figured I would ask here on the list before > digging > out a copy of tcpdump and going down that rabbit hole. > > I can mount and use NFSv3 shares just fine with ESXi from this same > server, and > can mount the same shares as NFSv4 from other clients (e.g. OS X) as > well. > This is NFSv4.1 specific, so NFSv4.0 should work, I think. Or just use NFSv3. rick > Thanks, > > Mahmoud Al-Qudsi > NeoSmart Technologies > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org" >