Date: Wed, 11 Jul 2018 12:08:48 +0000 From: bugzilla-noreply@freebsd.org To: stable@FreeBSD.org Subject: [Bug 229694] [zfs] unkillable "zpool scrub" in [tx->tx_sync_done_cv] state for damaged data Message-ID: <bug-229694-1689-q4etMGxVT8@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-229694-1689@https.bugs.freebsd.org/bugzilla/> References: <bug-229694-1689@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=3D229694 --- Comment #1 from Andriy Gapon <avg@FreeBSD.org> --- I am not too surprised. The pool configuration is not redundant and the wh= ole top level vdev is corrupted. I suspect that the scrub command needs to wri= te something to the pool to record the initial scrub state. And it's quite li= kely that it needs to perform Read-Modify-Write. And the read fails and the pool gets suspended. zpool scrub command is stuck waiting for confirmation that= the scrub is actually started. procstat -kk -a would paint a fuller picture. Maybe there is something reported in dmesg too, but not sure. --=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-229694-1689-q4etMGxVT8>