From owner-freebsd-fs@FreeBSD.ORG  Mon Oct  6 17:02:26 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 CA69FF08
 for <freebsd-fs@freebsd.org>; Mon,  6 Oct 2014 17:02:26 +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 857E39FB
 for <freebsd-fs@freebsd.org>; Mon,  6 Oct 2014 17:02:26 +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 s96H2OFW094803
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256
 verify=FAIL CN=khavrinen.csail.mit.edu issuer=Client+20CA);
 Mon, 6 Oct 2014 13:02:24 -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 s96H2ORA094800;
 Mon, 6 Oct 2014 13:02:24 -0400 (EDT) (envelope-from wollman)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <21554.52000.530951.15561@khavrinen.csail.mit.edu>
Date: Mon, 6 Oct 2014 13:02:24 -0400
From: Garrett Wollman <wollman@csail.mit.edu>
To: Rick Macklem <rmacklem@uoguelph.ca>
Subject: Re: 9.3 NFS client bug?
In-Reply-To: <1265026957.57440085.1412374216862.JavaMail.root@uoguelph.ca>
References: <21551.6675.236161.476053@khavrinen.csail.mit.edu>
 <1265026957.57440085.1412374216862.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]); Mon, 06 Oct 2014 13:02:24 -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: Mon, 06 Oct 2014 17:02:26 -0000

<<On Fri, 3 Oct 2014 18:10:16 -0400 (EDT), Rick Macklem <rmacklem@uoguelph.ca> said:

> 2 - Try an "oldnfs" mount and see if the old client exhibits the same behaviour.

Same behavior both old and new.  I'm doing binary search now to try to
minimize the size of the workload that exhibits the issue.

-GAWollman