Date: Fri, 06 Apr 2018 11:10:26 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 203906] ZFS lockup, spa_namespace_lock Message-ID: <bug-203906-3630-V4Kn3LHgH9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-203906-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-203906-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=3D203906 --- Comment #7 from Andriy Gapon <avg@FreeBSD.org> --- (In reply to emz from comment #6) A rather wild guess, but I suspect that it may had to do with the hardware. I see that ZFS was just blocked waiting for I/O. I do not see intrinsic problems with it. Maybe a disk took a nap or a command like TRIM blocked its operation for a = long time or something of that nature. A suspicious thread: 0 101671 kernel zio_free_issue_3_0 _mtx_lock_spin_cookie+= 0xc1 callout_lock+0xcb callout_reset_sbt_on+0x79 mprsas_action+0xf2d xpt_run_devq+0x48a xpt_action_default+0x8fc dastart+0x2f3 xpt_run_allocq+0x= 173 dastrategy+0x8d g_disk_start+0x34f g_io_request+0x2a7 zio_vdev_io_start+0x2= ae zio_execute+0xac zio_nowait+0xcb vdev_raidz_io_start+0x6cc zio_vdev_io_start+0x2ae zio_execute+0xac zio_nowait+0xcb Try to examine your system logs, maybe RAID event log too. --=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-203906-3630-V4Kn3LHgH9>