From owner-freebsd-fs@FreeBSD.ORG  Tue Oct  7 16:22:28 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 A9872661
 for <freebsd-fs@freebsd.org>; Tue,  7 Oct 2014 16:22:28 +0000 (UTC)
Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 82D81984
 for <freebsd-fs@freebsd.org>; Tue,  7 Oct 2014 16:22:28 +0000 (UTC)
Received: from jhbbsd.localnet (unknown [209.249.190.124])
 by bigwig.baldwin.cx (Postfix) with ESMTPSA id 70686B9BB;
 Tue,  7 Oct 2014 12:22:27 -0400 (EDT)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-fs@freebsd.org
Subject: Re: 9.3 NFS client bug?
Date: Tue, 7 Oct 2014 11:18:00 -0400
User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; )
References: <1109402573.59384867.1412683413852.JavaMail.root@uoguelph.ca>
In-Reply-To: <1109402573.59384867.1412683413852.JavaMail.root@uoguelph.ca>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201410071118.00364.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7
 (bigwig.baldwin.cx); Tue, 07 Oct 2014 12:22:27 -0400 (EDT)
Cc: Garrett Wollman <wollman@csail.mit.edu>
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 16:22:28 -0000

On Tuesday, October 07, 2014 8:03:33 am Rick Macklem wrote:
> Garrett Wollman wrote:
> > <<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
> > 
> 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?
> (There is a diagnostic printf w.r.t. this for NFSv4, but not NFSv3,
>  so you might try an NFSv4 mount. The printf starts with "NFSv4 fileid > 32..".)
> 
> Since d_fileno in "struct dirent" is 32bits, NFS just truncates the
> 64bit fileid to 32bits (or fills the high order 32bits with 0s for the server).
> ZFS is known to generate fileids with non-zero high order 32bits->busted.
> (And not at all easy to fix. I actually have a somewhat hackish idea for
>  a way to make 64bit d_fileno values work without busting backwards compatibility.
>  I think I'll post that to freebsd-fs@ and see what others think?)

Also, does it exhibit if you NFS export a UFS filesystem instead of ZFS?

-- 
John Baldwin