Date: Tue, 24 May 2016 00:23: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-bmPzWlFUoM@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 #3 from Doug Luce <doug@freebsd.con.com> --- (In reply to Rick Macklem from comment #2) OK, did that on the same machine as before. A new npm install gives me something slightly different: PID TID COMM TDNAME KSTACK 21557 100965 node - mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d kern_kevent+0x401 sys_kevent+0x12a amd64_syscall+0x351 Xfast_syscall+0xfb 21557 101212 node V8 WorkerThread mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4aa __umtx_op_sem_wait+0x73 amd64_syscall+0x351 Xfast_syscall+0xfb 21557 101213 node V8 WorkerThread mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4aa __umtx_op_sem_wait+0x73 amd64_syscall+0x351 Xfast_syscall+0xfb 21557 101214 node - mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_wait+0x329 __umtx_op_wait_uint_private+0x83 amd64_syscall+0x351 Xfast_syscall+0xfb 21557 101215 node - mi_switch+0xe1 sleepq_wait+0= x3a sleeplk+0x15d __lockmgr_args+0x902 vop_stdlock+0x3c VOP_LOCK1_APV+0xab _vn_lock+0x43 zfs_lookup+0x3c2 zfs_freebsd_lookup+0x6d VOP_CACHEDLOOKUP_APV+0xa1 vfs_cache_lookup+0xd6 VOP_LOOKUP_APV+0xa1 lookup+0x59c namei+0x4d4 vn_open_cred+0x21d kern_openat+0x26f amd64_syscall+0x351 Xfast_syscall+0xfb 21557 101646 node V8 WorkerThread mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4aa __umtx_op_sem_wait+0x73 amd64_syscall+0x351 Xfast_syscall+0xfb 21557 101651 node V8 WorkerThread mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_sem_wait+0x4aa __umtx_op_sem_wait+0x73 amd64_syscall+0x351 Xfast_syscall+0xfb 21557 101654 node - mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_wait+0x329 __umtx_op_wait_uint_private+0x83 amd64_syscall+0x351 Xfast_syscall+0xfb 21557 101655 node - mi_switch+0xe1 sleepq_catch_signals+0xab sleepq_wait_sig+0xf _sleep+0x27d umtxq_sleep+0x125 do_wait+0x329 __umtx_op_wait_uint_private+0x83 amd64_syscall+0x351 Xfast_syscall+0xfb Process still hangs, acourse. --=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-bmPzWlFUoM>