From owner-freebsd-current@FreeBSD.ORG Tue Dec 22 17:44:34 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D452110656A3 for ; Tue, 22 Dec 2009 17:44:34 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 70D888FC13 for ; Tue, 22 Dec 2009 17:44:34 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApsEAC6UMEuDaFvJ/2dsb2JhbACDbsMXj3GDXVYEgWU X-IronPort-AV: E=Sophos;i="4.47,437,1257138000"; d="scan'208";a="58787524" Received: from ganges.cs.uoguelph.ca ([131.104.91.201]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 22 Dec 2009 12:44:33 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id 76F71FB808B; Tue, 22 Dec 2009 12:44:33 -0500 (EST) X-Virus-Scanned: amavisd-new at ganges.cs.uoguelph.ca Received: from ganges.cs.uoguelph.ca ([127.0.0.1]) by localhost (ganges.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VGJo1lE876zx; Tue, 22 Dec 2009 12:44:32 -0500 (EST) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by ganges.cs.uoguelph.ca (Postfix) with ESMTP id 0DAE5FB801A; Tue, 22 Dec 2009 12:44:32 -0500 (EST) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id nBMHrpG08200; Tue, 22 Dec 2009 12:53:51 -0500 (EST) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Tue, 22 Dec 2009 12:53:51 -0500 (EST) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Andrew Pantyukhin In-Reply-To: <20091222132309.GI24163@pollux.cenkes.org> Message-ID: References: <20091222132309.GI24163@pollux.cenkes.org> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-851401618-1261504431=:5334" Cc: freebsd-current@FreeBSD.org Subject: Re: NFSv4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2009 17:44:35 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---559023410-851401618-1261504431=:5334 Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Tue, 22 Dec 2009, Andrew Pantyukhin wrote: > > Could I bother you directly with some questions from time to time > or should I post to a mailing list? Either. The advantage of using something like freebsd-current@ is that it ends up in the email archive that others can search and later I suspect others will start using NFSv4 and be able to help with answers. (If others get upset w.r.t. the noise, you can blame me:-) > > Here are a few: > - is ACL support coming to the FreeBSD NFSv4 client? Good question. As far as I'm aware, all the pieces are in FreeBSD8.0, but it didn't get tested. (The server wasn't quite there, but should be soon for freebsd-current using ZFS. At that point, I suspect it'll get tested. You can be the first!) > - I can't create Unix domain sockets in a mounted v4 file system > in FreeBSD 8.0, is that expected? I'd say that's a bug. I'll try it here and see what happens. > - is freebsd-rpcsec.patch coming to our head? Or rather, the > dependant functionality (per-user GSS context) > If you are referring to the experimental patch I have for FreeBSD8.0 that does host based initiator credentials from a keytab file, no. (It's too ugly, but I haven't come up with another way to make it work yet.) I believe that mounts done by a user (not root) that does a mount when holding a valid TGT does work without the patch. > A more general question: I'm currently using v3 (oldnfs) on > FreeBSD quite extensively =E2=80=94 my homedir and lots of other data is > mounted this way. When I try newnfs, both v3 and v4, they either > don't allow a desktop environment to start at all, or, if the > homedir is oldnfs-mounted, newnfs functions for other data for > some time, and then some problems start. Like, svnsync/csup > unable to get locks and such. Would you say it is expected > behaviour or do you consider newnfs mostly production quality > just a little while from "general deployment"? > > I mean, when do you think you'll be able to unlabel newnfs as > experimental? > Well, I wasn't aware of client side problems and what I've tested worked for me. (I'll admit I'm not the sort to use X or gui desktops.) The NFSv4 locking has worked ok for me against a Solaris10 server, but I haven't had much opportunity to test against Netapp. If you could reproduce a case of locking problems with an NFSv4 mount and then email me the raw tcpdump capture, I can go through the packet trace under wire shark and see what seems to have happened. (I am trying to avoid the NLM, since that's dfr@'s world and I know diddly about it.) I'd guess it's labelled experimental for at least the FreeBSD8 release cycle, rick ---559023410-851401618-1261504431=:5334--