From owner-freebsd-current@FreeBSD.ORG Wed Jul 23 18:02:40 2008 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 DAF5B1065709; Wed, 23 Jul 2008 18:02:40 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.freebsd.org (Postfix) with ESMTP id AB6598FC25; Wed, 23 Jul 2008 18:02:40 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from max.local (rrcs-74-218-226-253.se.biz.rr.com [74.218.226.253]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id m6NI2dJP009816; Wed, 23 Jul 2008 14:02:40 -0400 (EDT) (envelope-from lists@jnielsen.net) From: John Nielsen To: freebsd-current@freebsd.org Date: Wed, 23 Jul 2008 14:02:59 -0400 User-Agent: KMail/1.9.7 References: <200807221128.27592.lists@jnielsen.net> <20080723082401.GC3603@garage.freebsd.pl> In-Reply-To: <20080723082401.GC3603@garage.freebsd.pl> X-Face: #X5#Y*q>F:]zT!DegL3z5Xo'^MN[$8k\[4^3rN~wm=s=Uw(sW}R?3b^*f1Wu*.<=?utf-8?q?of=5F4NrS=0A=09P*M/9CpxDo!D6?=)IY1w<9B1jB; tBQf[RU-R<,I)e"$q7N7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807231402.59893.lists@jnielsen.net> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on ns1.jnielsen.net X-Virus-Status: Clean Cc: Pawel Jakub Dawidek , fs@freebsd.org Subject: Re: NFS writes and ZFS 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: Wed, 23 Jul 2008 18:02:41 -0000 On Wednesday 23 July 2008, Pawel Jakub Dawidek wrote: > On Tue, Jul 22, 2008 at 11:28:27AM -0400, John Nielsen wrote: > > I have a FreeBSD server (which I use as a NAS device, among other > > things) and a FreeBSD deskop. The desktop is running 7-STABLE from a > > couple days ago and the server is running 8-CURRENT from yesterday. The > > server has several NFS-exported ZFS'es which I mount from the desktop. > > Since moving the shares to ZFS I've been having trouble writing to them > > from the desktop--the mount hangs after the first or second attempt. > > This is similar if not identical to what's described in the thread > > (from -current) I partially copied below. > > > > Today I discovered that the problem seems to go away if I change the > > NFS mount options on the desktop. The following is a summary/timeline > > of what I've tried: > > > > 7-STABLE client, no NFS options (defaults); 7-STABLE server, UFS; works > > 7-STABLE client, no NFS options (defaults); 7-STABLE server, ZFS; > > broken 7-STABLE client, no NFS options (defaults); 8-CURRENT server, > > ZFS; broken 7-STABLE client, tcp,nfsv3,-r32768,-w32768; 8-CURRENT > > server, ZFS, works > > Do you need all the options here? If not, could you try to find the > smallest subset of options that are needed to make ZFS work? Maybe > 'nfsv3' is all that is needed, or 'tcp' alone fixes it? At work we use > many NFS exported ZFS file systems, mostly accessed from MacOS X and > we see no problems. No. "tcp" alone fixes it. That's not too surprising since nfsv3 should be a no-op. With everything _but_ "tcp" it took only slightly longer to hang the mount (not scientifically measured). With the default NFS mount mode changed to TCP in -CURRENT the workaround is already in place for FreeBSD clients, and the issue apparently never popped up on other clients--there are a few people (yourself included) who say they've never had a problem with Mac OS, e.g.. I haven't come across reports either way about Solaris or Linux. Are we the last ones to use UDP by default? Anyway, I hope this is helpful. Let me know if I should file a PR or anything. Thanks, JN