[Bug 209158] node / npm triggering zfs rename deadlock
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri Jul 15 00:33:51 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209158
robert.ayrapetyan at gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |robert.ayrapetyan at gmail.com
--- Comment #34 from robert.ayrapetyan at gmail.com ---
Same with node 6.3.0:
procstat -kk 95115
PID TID COMM TDNAME KSTACK
95115 101118 node - mi_switch+0xe1
thread_suspend_switch+0x170 thread_single+0x4e5 exit1+0xce sigexit+0x925
postsig+0x286 ast+0x427 doreti_ast+0x1f
95115 101294 node V8 WorkerThread mi_switch+0xe1
thread_suspend_switch+0x170 cursig+0x613 ast+0x42f doreti_ast+0x1f
95115 101301 node V8 WorkerThread mi_switch+0xe1
thread_suspend_switch+0x170 cursig+0x613 ast+0x42f doreti_ast+0x1f
95115 101303 node V8 WorkerThread mi_switch+0xe1
thread_suspend_switch+0x170 cursig+0x613 ast+0x42f doreti_ast+0x1f
95115 101305 node - mi_switch+0xe1 sleepq_wait+0x3a
sleeplk+0x15d __lockmgr_args+0x91a vop_stdlock+0x3c VOP_LOCK1_APV+0xab
_vn_lock+0x43 vget+0x73 cache_lookup+0x5d5 vfs_cache_lookup+0xac
VOP_LOOKUP_APV+0xa1 lookup+0x5a1 namei+0x4d4 kern_renameat+0x1b7
amd64_syscall+0x40f Xfast_syscall+0xfb
95115 101312 node - mi_switch+0xe1 sleepq_wait+0x3a
sleeplk+0x15d __lockmgr_args+0x91a vop_stdlock+0x3c VOP_LOCK1_APV+0xab
_vn_lock+0x43 vget+0x73 cache_lookup+0x5d5 vfs_cache_lookup+0xac
VOP_LOOKUP_APV+0xa1 lookup+0x5a1 namei+0x4d4 kern_renameat+0x1b7
amd64_syscall+0x40f Xfast_syscall+0xfb
95115 101313 node - mi_switch+0xe1 sleepq_wait+0x3a
sleeplk+0x15d __lockmgr_args+0xca0 vop_stdlock+0x3c VOP_LOCK1_APV+0xab
_vn_lock+0x43 vputx+0x21f zfs_rename_unlock+0x3e zfs_freebsd_rename+0xe39
VOP_RENAME_APV+0xab kern_renameat+0x4a6 amd64_syscall+0x40f Xfast_syscall+0xfb
95115 101314 node - mi_switch+0xe1 sleepq_wait+0x3a
sleeplk+0x15d __lockmgr_args+0x91a vop_stdlock+0x3c VOP_LOCK1_APV+0xab
_vn_lock+0x43 zfs_lookup+0x45d zfs_freebsd_lookup+0x6d
VOP_CACHEDLOOKUP_APV+0xa1 vfs_cache_lookup+0xd6 VOP_LOOKUP_APV+0xa1
lookup+0x5a1 namei+0x4d4 kern_renameat+0x1b7 amd64_syscall+0x40f
Xfast_syscall+0xfb
Nasty node, it really does something very unusual with files, whenever I met
this issue it was always caused by node process, this is really funny...
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-fs
mailing list