From owner-freebsd-fs@freebsd.org  Wed Sep 23 16:38:22 2015
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@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 2BA9FA064D9
 for <freebsd-fs@mailman.ysv.freebsd.org>; Wed, 23 Sep 2015 16:38:22 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (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 18B661ED6
 for <freebsd-fs@FreeBSD.org>; Wed, 23 Sep 2015 16:38:22 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t8NGcLYp096493
 for <freebsd-fs@FreeBSD.org>; Wed, 23 Sep 2015 16:38:21 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 198457] zfs acl lost after zfs send-receive. Kernel panic
Date: Wed, 23 Sep 2015 16:38:22 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: o.bende@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-198457-3630-lfNjJjgYuJ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-198457-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-198457-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/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: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2015 16:38:22 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198457

--- Comment #4 from o.bende@gmail.com ---
Thanks for your Comment.
I think the main problem is not the handling of the error, but that there is an
error! I can (probably) understand, why the system should panic because of such
a file-system issue - but why is there this issue? Summary:
Why are the ACLs broken after replication?

And another question: Why do you think we should contact ZoL? I always thought,
ZoL and FreeBSD ZFS are two different systems?! Actually, I did not choose ZoL
because it is not really defined production-ready - but FreeBSD ZFS is.

-- 
You are receiving this mail because:
You are the assignee for the bug.