Date: Tue, 24 May 2016 15:00:08 +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-kYNAT7xrnH@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 Bengt Ahlgren <bengta@sics.se> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bengta@sics.se --- Comment #10 from Bengt Ahlgren <bengta@sics.se> --- (In reply to Andriy Gapon from comment #9) You write that you think that a zfs rename (file, NOT snapshot) deadlock has been around for a long time. Do you think this could be the same issue (on 9.3)? https://lists.freebsd.org/pipermail/freebsd-fs/2015-December/022370.html The trigger there was a massively parallel java program creating (and renam= ing) a lot of output files. I would be interested in testing patches, but that server is unfortunately still running 9.3. Later in the summer perhaps. --=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-kYNAT7xrnH>