From owner-freebsd-fs@FreeBSD.ORG Fri Oct 3 21:50:13 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 829E0DC0 for ; Fri, 3 Oct 2014 21:50:13 +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 468E5B9C for ; Fri, 3 Oct 2014 21:50:13 +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 s93LoBfA025619 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL CN=khavrinen.csail.mit.edu issuer=Client+20CA) for ; Fri, 3 Oct 2014 17:50:11 -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 s93LoBAu025616; Fri, 3 Oct 2014 17:50:11 -0400 (EDT) (envelope-from wollman) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <21551.6675.236161.476053@khavrinen.csail.mit.edu> Date: Fri, 3 Oct 2014 17:50:11 -0400 From: Garrett Wollman To: freebsd-fs@freebsd.org Subject: 9.3 NFS client bug? 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]); Fri, 03 Oct 2014 17:50:11 -0400 (EDT) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Oct 2014 21:50:13 -0000 I've been doing some NFS testing, and found some issues with the NFS client in 9.3. This is pretty easily reproducible with bonnie++, but I haven't tried to reduce the size of the workload to make it easier to test or trace. ##### NFSv3 mount, 9.3 client from 9.3 server # bonnie++ -s 0 -n 1024:65536:0:1023:16384 -u 4294967294 -D Using uid:-2, gid:65533. Create files in sequential order...done. Stat files in sequential order...done. Delete files in sequential order...Bonnie: drastic I/O error (rmdir): Directory not empty Cleaning up test directory after error. Identical behavior is observed for a 9.3 client talking to a 9.1 server, and for NFSv4 mounts, but NOT for an Ubuntu 14.04 client talking to the 9.3 server using either NFSv3 or NFSv4. I haven't tried using a 9.2 or 9.1 client (yes, I still have some machines running 9.1 here) to see if the issue is a recently introduced one, nor have I traced the client or server code to see what's actually going on. Has anyone seen this before? -GAWollman