summaryrefslogtreecommitdiffstats
path: root/man
diff options
context:
space:
mode:
authorTom Caputi <[email protected]>2019-05-01 20:34:24 -0400
committerBrian Behlendorf <[email protected]>2019-05-01 17:34:24 -0700
commit85bdc6840190879e4b97364dfa6d93e2877a265e (patch)
tree8bdf9aafd812e3285adcc91438c8863738e40988 /man
parent6bdefad311a87452b557febd5be33b627775a006 (diff)
Fix estimated scrub completion time
Currently, it is possible for the 'zpool scrub' command to progress slightly beyond 100% due to concurrent changes happening on the live pool. This behavior is expected, but the userspace code for 'zpool status' would subtract the expected amount of data from the amount of data already scrubbed, resulting in a negative integer being casted to a large positive one. This number was then used to calculate the estimated completion time, resulting in wildly wrong results. This code changes the behavior so that 'zpool status' does not attempt to report an estimate during this period. Reviewed by: Brian Behlendorf <[email protected]> Reviewed-by: Igor Kozhukhov <[email protected]> Reviewed-by: George Melikov <[email protected]> Signed-off-by: Tom Caputi <[email protected]> Closes #8611 Closes #8687
Diffstat (limited to 'man')
-rw-r--r--man/man8/zpool.84
1 files changed, 4 insertions, 0 deletions
diff --git a/man/man8/zpool.8 b/man/man8/zpool.8
index 76bc1cf74..eb93d3bb3 100644
--- a/man/man8/zpool.8
+++ b/man/man8/zpool.8
@@ -2189,6 +2189,10 @@ If a scrub is paused, the
resumes it.
If a resilver is in progress, ZFS does not allow a scrub to be started until the
resilver completes.
+.Pp
+Note that, due to changes in pool data on a live system, it is possible for
+scrubs to progress slightly beyond 100% completion. During this period, no
+completion time estimate will be provided.
.Bl -tag -width Ds
.It Fl s
Stop scrubbing.