From owner-freebsd-current@freebsd.org Thu Aug 11 08:04:19 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06093BB54A8 for ; Thu, 11 Aug 2016 08:04:19 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BE2A01D65 for ; Thu, 11 Aug 2016 08:04:18 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1bXkyO-0011Tt-Gn>; Thu, 11 Aug 2016 10:04:16 +0200 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=freyja.zeit4.iv.bundesimmobilien.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1bXkyO-000jXT-6N>; Thu, 11 Aug 2016 10:04:16 +0200 Date: Thu, 11 Aug 2016 10:04:11 +0200 From: "O. Hartmann" To: freebsd-current Subject: CURRENT: NFSv4/autofs and ZFS weirdness: permission denied Message-ID: <20160811100411.2d30546f@freyja.zeit4.iv.bundesimmobilien.de> Organization: FU Berlin X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 87.138.105.249 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2016 08:04:19 -0000 Both server and clients are running most recent 12-CURRENT. The server is exporting a ZFS volume via NFSv4. I recently copied that volume from another volume via zfs send/receive from one vilume on the same server to another volume, created on another sorage device. The specific volume worked before in the environment I use. It is exported via NFSv4 by the server with -maproot=www:www and read/writeable by only one specific host and imported via NFSv4 autofs by that specific host. The purpose is to synchronize via "rsync -rv" packages created via poudriere on a very fast smaller machine to the fileserver. The owner of the volume's folder hierarchy is "www:www" with unaltered, proper access rights. The last time the sync worked was July, 20th. Now, since a couple of days or weeks, I get an error: permission denied. root is the user trying to rsync from the poudriere creator host to write the packages folder hierarchy and packages to the autofs volume, but the procedure fails. I have no clue what changed. I checked whether the ZFS volume is locked in any way after it has been sent/received, but it isn't. It looks like an ordinary volume and locally (from the perspective of the fileserver) creation and deletion of files is possible. What do I miss here? The fact that this procedure worked with 11-CURRENT and 11-ALPHA weeks ago as it is, makes me suspect a bug or fundamentaly change in the bahviour or - there is a hidden lock when zfs send/receive is used I didn't realizes to relief. Thanks in advance for help and considerations, Oliver