Date: Mon, 22 Jun 2009 14:10:03 GMT From: Gavin Atkinson <gavin@FreeBSD.org> To: freebsd-fs@FreeBSD.org Subject: Re: kern/135412: ZFS issue Message-ID: <200906221410.n5MEA3uQ061414@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/135412; it has been noted by GNATS. From: Gavin Atkinson <gavin@FreeBSD.org> To: bug-followup@FreeBSD.org Cc: Danny Braniss <danny@cs.huji.ac.il> Subject: Re: kern/135412: ZFS issue Date: Mon, 22 Jun 2009 14:30:27 +0100 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"?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200906221410.n5MEA3uQ061414>