Date: Mon, 04 Mar 2019 15:18:35 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 236220] ZFS vnode deadlock Message-ID: <bug-236220-227-jCtuH8vJkZ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-236220-227@https.bugs.freebsd.org/bugzilla/> References: <bug-236220-227@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=3D236220 --- Comment #1 from ncrogers@gmail.com --- avg@freebsd.org pointed out in the freebsd-stable list that one thread is s= tuck on zfs_znode_alloc, and that is likely the root of the problem. Indeed all = the systems I've witnessed this happen to have had one thread stuck on vn_lock = -> zfs_znode_alloc. It often seems to be a different application, so I'm still= not sure what particular workload is causing this. For example, the below lines from procstat -kka are from three different systems stuck in a hung / zfs deadlock state. 2329 100515 sh - mi_switch+0xe1 sleepq_wait+0x2c sleeplk+0x1c5 lockmgr_xlock_hard+0x19c VOP_LOCK1_APV+0x7e _vn_lock+0x40 zfs_znode_alloc+0x434 zfs_mknode+0xa9d zfs_freebsd_create+0x5= 12 VOP_CREATE_APV+0x78 vn_open_cred+0x2c9 kern_openat+0x20c amd64_syscall+0x369 fast_syscall_common+0x101=20 36704 101146 perl - mi_switch+0xe1 sleepq_wait+0x2c sleeplk+0x1c5 lockmgr_xlock_hard+0x19c VOP_LOCK1_APV+0x7e _vn_lock+0x40 zfs_znode_alloc+0x434 zfs_mknode+0xa9d zfs_freebsd_create+0x5= 12 VOP_CREATE_APV+0x78 vn_open_cred+0x2c9 kern_openat+0x20c amd64_syscall+0x369 fast_syscall_common+0x101=20 1663 100503 postgres - mi_switch+0xe1 sleepq_wait+0x2c sleeplk+0x1c5 lockmgr_xlock_hard+0x19c VOP_LOCK1_APV+0x7e _vn_lock+0x40 zfs_znode_alloc+0x434 zfs_mknode+0xa9d zfs_freebsd_create+0x5= 12 VOP_CREATE_APV+0x78 vn_open_cred+0x2c9 kern_openat+0x20c amd64_syscall+0x369 fast_syscall_common+0x101 --=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-236220-227-jCtuH8vJkZ>