aboutsummaryrefslogtreecommitdiffstats
path: root/module/zfs/dsl_pool.c
diff options
context:
space:
mode:
authorMatthew Ahrens <[email protected]>2017-05-10 10:32:40 -0700
committerBrian Behlendorf <[email protected]>2017-05-10 10:32:39 -0700
commit335b251ac1a1f8ba8434450dc0f24986bc44f688 (patch)
treefe18fde37c7f1c9eaaff8f2ee681a086a37bacef /module/zfs/dsl_pool.c
parentf486f58440cc6bf7e699aa2870da142a83cac04e (diff)
OpenZFS 8166 - zpool scrub thinks it repaired offline device
Authored by: Matthew Ahrens <[email protected]> Reviewed by: George Wilson <[email protected]> Reviewed-by: loli10K <[email protected]> Reviewed-by: Brian Behlendorf <[email protected]> Ported-by: Matthew Ahrens <[email protected]> If we do a scrub while a leaf device is offline (via "zpool offline"), we will inadvertently clear the DTL (dirty time log) of the offline device, even though it is still damaged. When the device comes back online, we will incompletely resilver it, thinking that the scrub repaired blocks written before the scrub was started. The incomplete resilver can lead to data loss if there is a subsequent failure of a different leaf device. The fix is to never clear the DTL of offline devices. Note that if a device is onlined while a scrub is in progress, the scrub will be restarted. The problem can be worked around by running "zpool scrub" after "zpool online". OpenZFS-issue: https://www.illumos.org/issues/8166 OpenZFS-commit: https://github.com/openzfs/openzfs/pull/372 Closes #5806 Closes #6103
Diffstat (limited to 'module/zfs/dsl_pool.c')
0 files changed, 0 insertions, 0 deletions