From owner-freebsd-fs@FreeBSD.ORG Wed Feb 29 18:57:17 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5FB9A106566B; Wed, 29 Feb 2012 18:57:17 +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 155988FC13; Wed, 29 Feb 2012 18:57:16 +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 q1TIvGb6038966; Wed, 29 Feb 2012 13:57:16 -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 q1TIvGN2038963; Wed, 29 Feb 2012 13:57:16 -0500 (EST) (envelope-from wollman) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <20302.29963.529821.258448@hergotha.csail.mit.edu> Date: Wed, 29 Feb 2012 13:57:15 -0500 From: Garrett Wollman To: freebsd-fs@freebsd.org 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 13:57:16 -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: rmacklem@freebsd.org Subject: 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: Wed, 29 Feb 2012 18:57:17 -0000 I'm testing out a new file server, and trying to rsync files from a proprietary NAS to the box I'm testing. It's running the new NFS code and 9.0. rsync frequently and repeatably errors out with something like this: rsync: read errors mapping "[source file name]": Resource temporarily unavailable (35) cp(1), on the other hand, seems just fine with the same source files. Any ideas what causes this? -GAWollman