Date: Thu, 22 Dec 2016 13:05:49 +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-FKLCLdbYfS@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 paul@ifdnrg.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |paul@ifdnrg.com --- Comment #48 from paul@ifdnrg.com --- I believe i am seeing activity related to this PR We're finding that npm gets stuck in updates, and if the parent is=20 killed, it leaves a process in uninterruptible state (this has not even been killlable during shutdown and a previous box=20 with same symptoms has needed a hard reset) Child processes get stuck in a DN state, it does not seem to matter if npm = or node was running prior to update, as npm is called as part of the update process. This also seems to be affecting separate periodic scripts such as 100.check= suid which also become stuck. We now have 5 boxes in this state, and i suspect all will need a hard reboo= t to clear. Systems are FreeBSD 10.3-REL on ZFS --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-209158-3630-FKLCLdbYfS>