From owner-freebsd-fs@freebsd.org  Tue Apr 18 15:08:50 2017
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 8C408D42793
 for <freebsd-fs@mailman.ysv.freebsd.org>; Tue, 18 Apr 2017 15:08:50 +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 7B4A5131
 for <freebsd-fs@FreeBSD.org>; Tue, 18 Apr 2017 15:08:50 +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 v3IF8jDR076181
 for <freebsd-fs@FreeBSD.org>; Tue, 18 Apr 2017 15:08:50 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 209158] node / npm triggering zfs rename deadlock
Date: Tue, 18 Apr 2017 15:08:46 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: needs-qa, patch
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: bugs.freebsd.org@lpz.yellowspace.net
X-Bugzilla-Status: Closed
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: avg@FreeBSD.org
X-Bugzilla-Flags: mfc-stable10? mfc-stable11?
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-209158-3630-mXGZeNg42K@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-209158-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-209158-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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.23
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: Tue, 18 Apr 2017 15:08:50 -0000

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

Lorenzo <bugs.freebsd.org@lpz.yellowspace.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bugs.freebsd.org@lpz.yellow
                   |                            |space.net

--- Comment #51 from Lorenzo <bugs.freebsd.org@lpz.yellowspace.net> ---
(In reply to Michael Gmelin from comment #50)

+1 on this. Any chance to have the fix merged on 10.3? I can reliably repro=
duce
the problem at any time on 10.3-RELEASE-p11/-p17 with an nmp install. It is
quite a show blocker, and we're relying on LTS releases (10.3-RELEASE being=
 the
only one currently)...

--=20
You are receiving this mail because:
You are on the CC list for the bug.=