Date: Tue, 24 May 2016 12:02:03 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 209158] node / npm triggering zfs rename deadlock Message-ID: <bug-209158-3630-wkZ8blECiu@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/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209158 --- Comment #6 from Rick Macklem <rmacklem@FreeBSD.org> --- I knew there was a ZFS rename issue, but I thought it occurred rarely and typically (always??) when snapshots were being renamed. This problem seems to have become frequent. Of course, just about any change could cause changes in when things get executed and "tickle" the deadlock bug. There was a case on freefall that looked similar (due to a deadlock involving vnode locks, mostly through cache_lookup()) and I had "hoped" this was the same problem (since the freefall case occurred once in several months). It doesn't appear to be the same problem. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209158-3630-wkZ8blECiu>