From owner-freebsd-fs@FreeBSD.ORG Thu Mar 1 01:52:16 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 377D7106567C for ; Thu, 1 Mar 2012 01:52:16 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (wollman-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:ccb::2]) by mx1.freebsd.org (Postfix) with ESMTP id C0B538FC25 for ; Thu, 1 Mar 2012 01:52:15 +0000 (UTC) Received: from hergotha.csail.mit.edu (localhost [127.0.0.1]) by hergotha.csail.mit.edu (8.14.4/8.14.4) with ESMTP id q211qEuE051449; Wed, 29 Feb 2012 20:52:14 -0500 (EST) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.14.4/8.14.4/Submit) id q211qEnC051446; Wed, 29 Feb 2012 20:52:14 -0500 (EST) (envelope-from wollman) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <20302.54862.344852.13627@hergotha.csail.mit.edu> Date: Wed, 29 Feb 2012 20:52:14 -0500 From: Garrett Wollman To: Rick Macklem In-Reply-To: <148631084.149332.1330561285089.JavaMail.root@erie.cs.uoguelph.ca> References: <20302.29963.529821.258448@hergotha.csail.mit.edu> <148631084.149332.1330561285089.JavaMail.root@erie.cs.uoguelph.ca> X-Mailer: VM 7.17 under 21.4 (patch 22) "Instant Classic" XEmacs Lucid X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (hergotha.csail.mit.edu [127.0.0.1]); Wed, 29 Feb 2012 20:52:14 -0500 (EST) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hergotha.csail.mit.edu Cc: freebsd-fs@freebsd.org Subject: Re: Under what circumstances does the new NFS client return EAGAIN? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Mar 2012 01:52:16 -0000 < said: > If you are using the "soft" or "intr" mount options, I'd suggest you > get rid of them (technically "intr" should result in EINTR, but I wouldn't > be surprised if an EWOULDBLOCK could pop out, as well). Also, you > didn't mention whether you were using UDP or TCP mounts, although the > above comments should apply to both. mount -t nfs -o ro,hard,tcp,nointr > You might also want to capture packets and look at them in wireshark, > to make sure the EWOULDBLOCK isn't coming from the proprietary NAS server. Unfortunately, I can't capture packets on this machine fast enough to record a decodeable NFS/TCP stream with the NAS. Another bug I've noticed: when mounting any remote NFS filesystem, all of the local exported NFS filesystems briefly give [EPERM] (or maybe it's [EACCES]) errors to their clients. This tends to break whatever is trying to use them at the time. It doesn't happen when local ZFS datasets are created and mounted. -GAWollman