From owner-freebsd-current@FreeBSD.ORG Wed Jul 23 09:05:02 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 286E6106566C; Wed, 23 Jul 2008 09:05:02 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 6F0658FC15; Wed, 23 Jul 2008 09:05:01 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id m6N94wr8048538 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 23 Jul 2008 11:04:59 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by cicely5.cicely.de (8.14.2/8.14.2) with ESMTP id m6N94q1h087198 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Jul 2008 11:04:52 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id m6N94qNX064591; Wed, 23 Jul 2008 11:04:52 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id m6N94pvX064590; Wed, 23 Jul 2008 11:04:51 +0200 (CEST) (envelope-from ticso) Date: Wed, 23 Jul 2008 11:04:51 +0200 From: Bernd Walter To: Pawel Jakub Dawidek Message-ID: <20080723090450.GV58113@cicely7.cicely.de> References: <200807221128.27592.lists@jnielsen.net> <20080723082401.GC3603@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080723082401.GC3603@garage.freebsd.pl> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED=-1.8, AWL=0.141, BAYES_00=-2.599 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on spamd.cicely.de Cc: John Nielsen , current@freebsd.org, fs@freebsd.org Subject: Re: NFS writes and ZFS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de 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 09:05:02 -0000 On Wed, Jul 23, 2008 at 10:24:01AM +0200, 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. Whenever changing NFS transport options has an influence on reliability my first task is to verify the network. Especially there were often hardware problems with some NIC lately, of which some have worked around in the drivers and some not. Disabling TSO and checksum offloading typically helps. This kind of problem is typical on both the client and server, but also on routers. Of course network problems can also be on any cable, switch in between as well, but are less typical to produce complete NFS hangs. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.