aboutsummaryrefslogtreecommitdiff
path: root/contrib/llvm-project/lldb/source/Plugins/ScriptInterpreter/Python/Interfaces/ScriptedPythonInterface.cpp
diff options
context:
space:
mode:
authorPavel Snajdr <snajpa@snajpa.net>2024-10-04 17:41:17 +0000
committerGitHub <noreply@github.com>2024-10-04 17:41:17 +0000
commit0d77e738e65d2fdc37c9c345c022f14239ae67cb (patch)
tree9f323470fc410f20566946112f68ffdbc83a1c82 /contrib/llvm-project/lldb/source/Plugins/ScriptInterpreter/Python/Interfaces/ScriptedPythonInterface.cpp
parent3d0175d10e1114aaf94255c09f6d9ad45a333255 (diff)
Defer resilver only when progress is above a threshold
Restart a resilver from scratch, if the current one in progress is below a new tunable, zfs_resilver_defer_percent (defaulting to 10%). The original rationale for deferring additional resilvers, when there is already one in progress, was to help achieving data redundancy sooner for the data that gets scanned at the end of the resilver. But in case the admin wants to attach multiple disks to a single vdev, it wasn't immediately obvious the admin is supposed to run `zpool resilver` afterwards to reset the deferred resilvers and start a new one from scratch. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Pavel Snajdr <snajpa@snajpa.net> Closes #15810
Diffstat (limited to 'contrib/llvm-project/lldb/source/Plugins/ScriptInterpreter/Python/Interfaces/ScriptedPythonInterface.cpp')
0 files changed, 0 insertions, 0 deletions