Date: Wed, 11 Jul 2018 11:10:29 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 229694] [zfs] unkillable "zpool scrub" in [tx->tx_sync_done_cv] state for damaged data Message-ID: <bug-229694-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229694 Bug ID: 229694 Summary: [zfs] unkillable "zpool scrub" in [tx->tx_sync_done_cv] state for damaged data Product: Base System Version: 11.2-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: stable@FreeBSD.org Reporter: eugen@freebsd.org CC: fs@FreeBSD.org Hi! "zpool scrub" may hang in an uninterruptable disk i/o state in case of damaged pool data for 11.2-STABLE/amd64 r335757. This is easily reproduceable using file-backed ZFS pool when files reside on another ("real") pool: cd dir # resides on ZFS size=100 rm -f vdev1 vdev2 truncate -s ${size}m vdev1 vdev2 zpool create ztest $(realpath vdev1) zpool add ztest $(realpath vdev2) # simulate data corruption dd if=/dev/urandom of=vdev2 bs=1m count=${size} zpool scrub ztest The last command "zpool scrub" always hangs here: load: 0.53 cmd: zpool 2130 [tx->tx_sync_done_cv] 34.59r 0.00u 0.00s 0% 3692k "kill -9" cannot kill it. -- 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-229694-3630>