From owner-freebsd-fs@FreeBSD.ORG  Mon Jun 22 15:20:04 2009
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id B8BAF106568A
	for <freebsd-fs@hub.freebsd.org>; Mon, 22 Jun 2009 15:20:04 +0000 (UTC)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id A71FA8FC21
	for <freebsd-fs@hub.freebsd.org>; Mon, 22 Jun 2009 15:20:04 +0000 (UTC)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n5MFK4Cu014925
	for <freebsd-fs@freefall.freebsd.org>; Mon, 22 Jun 2009 15:20:04 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n5MFK4Xr014924;
	Mon, 22 Jun 2009 15:20:04 GMT (envelope-from gnats)
Date: Mon, 22 Jun 2009 15:20:04 GMT
Message-Id: <200906221520.n5MFK4Xr014924@freefall.freebsd.org>
To: freebsd-fs@FreeBSD.org
From: Danny Braniss <danny@cs.huji.ac.il>
Cc: 
Subject: Re: kern/135412: ZFS issue 
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Danny Braniss <danny@cs.huji.ac.il>
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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, 22 Jun 2009 15:20:05 -0000

The following reply was made to PR kern/135412; it has been noted by GNATS.

From: Danny Braniss <danny@cs.huji.ac.il>
To: Gavin Atkinson <gavin@FreeBSD.org>
Cc: bug-followup@FreeBSD.org
Subject: Re: kern/135412: ZFS issue 
Date: Mon, 22 Jun 2009 17:53:44 +0300

 > Other useful information (from PR kern/135039):
 > 
 > This appears to only affect 7-STABLE since the ZFS merge, but doesn't
 > affect -HEAD.
 > 
 > After the recent import of ZFS v13 into 7-STABLE, an mkstemp() call from
 > an NFS client to a ZFS-backed NFS server will fail: the syscall returns
 > EIO and the server will have created a 0-byte file with 000 permissions.
 > This breaks not just mktemp but also mv, tar, rsync...
 > 
 > Kip Macy said there's a flags check that is too strict, in email message
 > <3c1674c90905280025i17039257l573838d33d8493fd@mail.gmail.com>
 > Otherwise, use cp and rm instead of mv, or use scp instead of NFS, or
 > use UFS2 on the server
 > 
 > To submitter: did you upgrade your on-disk pools to v13, or is running
 > the new code and v6 pools enough to show the problem?  What is the
 > output of "zpool upgrade"?
 
 it happens ONLY because zfs is v13, irrelevant if the pools have been upgraded,
 created, or not upgraded.
 so yes, just running a newer -stable is enough to show the problem.
 
 Since I am using ZFS + NFS, and providing service to several hundred users,
 telling them not to use tar, svn, rsync, etc is not an option :-)
 also, NFS V2 is broken/un-maintained.
 
 danny
 
 
 
 >