From owner-freebsd-fs@FreeBSD.ORG  Tue Oct  7 21:50:08 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id C1D32DF0;
 Tue,  7 Oct 2014 21:50:08 +0000 (UTC)
Received: from khavrinen.csail.mit.edu (khavrinen.csail.mit.edu
 [IPv6:2001:470:8b2d:1e1c:21b:21ff:feb8:d7b0])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "khavrinen.csail.mit.edu", Issuer "Client CA" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 81FA93E8;
 Tue,  7 Oct 2014 21:50:08 +0000 (UTC)
Received: from khavrinen.csail.mit.edu (localhost [127.0.0.1])
 by khavrinen.csail.mit.edu (8.14.7/8.14.7) with ESMTP id s97Lo61K006251
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256
 verify=FAIL CN=khavrinen.csail.mit.edu issuer=Client+20CA);
 Tue, 7 Oct 2014 17:50:06 -0400 (EDT)
 (envelope-from wollman@khavrinen.csail.mit.edu)
Received: (from wollman@localhost)
 by khavrinen.csail.mit.edu (8.14.7/8.14.7/Submit) id s97Lo611006248;
 Tue, 7 Oct 2014 17:50:06 -0400 (EDT) (envelope-from wollman)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <21556.24590.269326.188103@khavrinen.csail.mit.edu>
Date: Tue, 7 Oct 2014 17:50:06 -0400
From: Garrett Wollman <wollman@csail.mit.edu>
To: Rick Macklem <rmacklem@uoguelph.ca>
Subject: Re: 9.3 NFS client bug?
In-Reply-To: <603326314.59995969.1412715962746.JavaMail.root@uoguelph.ca>
References: <1109402573.59384867.1412683413852.JavaMail.root@uoguelph.ca>
 <603326314.59995969.1412715962746.JavaMail.root@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.4.3
 (khavrinen.csail.mit.edu [127.0.0.1]); Tue, 07 Oct 2014 17:50:06 -0400 (EDT)
Cc: freebsd-fs@freebsd.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Oct 2014 21:50:08 -0000

<<On Tue, 7 Oct 2014 17:06:02 -0400 (EDT), Rick Macklem <rmacklem@uoguelph.ca> said:

>> By ay chance is your ZFS server allocating a ZFS inode (whatever they
>> call it) with a fileno/inode# that doesn't fit in 32 bits?

Nope.  (And I want to emphasize that Ubuntu clients don't exhibit the
problem, so whatever it is, it doesn't appear to be related to the
backing filesystem on the server.)

> Btw, I tried your bonnie++ command on my test machines, but they failed
> part way through because they couldn't allocate boundary tags. (At least
> now I can reproduce that easily, although it is the M_NOWAIT case where
> the thread just loops in the kernel.)

You really need to get some server-class hardware.  Perhaps the
Foundation can help?

I'm currently using the following command, which seems to reproduce
the problem reliably on my client and server:

bonnie++ -s 0 -n 144:0:0:1:16384 -u 4294967294 -D

This minimizes the amount of temporary storage required.

-GAWollman