Date: Fri, 26 Oct 2018 16:55:06 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 229614] ZFS lockup in zil_commit_impl Message-ID: <bug-229614-3630-OipKbyltUq@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-229614-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-229614-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=3D229614 --- Comment #27 from Andreas Sommer <andreas.sommer87@googlemail.com> --- Issue appeared again, using the patched kernel: PID TID COMM TDNAME KSTACK [...] 1729 100862 python3.6 - mi_switch+0xe6 sleepq_wait+0x2c _sx_xlock_hard+0x306 zil_commit_impl+0x11d zfs_freebsd_putpages+0x635 VOP_PUTPAGES_APV+0x82 vnode_pager_putpages+0x8e vm_pageout_flush+0xea vm_object_page_collect_flush+0x213 vm_object_page_clean+0x146 vm_object_terminate+0x93 zfs_freebsd_reclaim+0x1e VOP_RECLAIM_APV+0x82 vgonel+0x208 vrecycle+0x4a zfs_freebsd_inactive+0xd VOP_INACTIVE_APV+0x82 vinactive+0xfc After applying the kernel patch on Oct 8th, the problem occurred on 22nd. Better interval than before, but here we are again. Could you give me some pointers how to debug this myself? --=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-229614-3630-OipKbyltUq>