From owner-freebsd-fs@FreeBSD.ORG Fri Sep 3 16:35:19 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFDA1106566C for ; Fri, 3 Sep 2010 16:35:19 +0000 (UTC) (envelope-from gull@gull.us) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id AE10D8FC16 for ; Fri, 3 Sep 2010 16:35:19 +0000 (UTC) Received: by vws7 with SMTP id 7so1635709vws.13 for ; Fri, 03 Sep 2010 09:35:18 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.251.197 with SMTP id mt5mr899462qcb.131.1283530088652; Fri, 03 Sep 2010 09:08:08 -0700 (PDT) Received: by 10.229.214.199 with HTTP; Fri, 3 Sep 2010 09:08:08 -0700 (PDT) X-Originating-IP: [69.91.158.135] In-Reply-To: References: Date: Fri, 3 Sep 2010 09:08:08 -0700 Message-ID: From: David Brodbeck To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Weird Linux - FreeBSD/ZFS NFSv4 interoperability problem 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: Fri, 03 Sep 2010 16:35:20 -0000 (Note: I originally posted this to freebsd-questions, and it was suggested I take it here.) While doing some interoperability testing between Linux and FreeBSD, I came up with this unusual issue. =A0I could use some help figuring out if this is a bug, and if so, where to file it. =A0Here's the scenario: - FreeBSD 8.1-RELEASE server, sharing a ZFS filesystem via NFSv4. - Linux client (I've tested with RHEL 5.4 and Debian Lenny) mounting said filesystem with NFSv4. - A user on the Linux client does a Subversion checkout onto the mounted filesystem. At the end of the checkout, access to the filesystem hangs. =A0nfsd on the FreeBSD server and rpciod on the Linux client seem to be in a tight loop, and there's lots of network traffic between them. =A0I can reproduce this every time. The problem does not occur if the backing filesystem is UFS instead of ZFS, if NFSv3 is used instead of NFSv4, or if the client is FreeBSD instead of Linux.