Pavel Snajdr 0d77e738e6 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		2024-10-04 10:41:17 -07:00
..
.gitignore	Add zpool events tests	2017-05-22 12:34:42 -04:00
blkdev.shlib	ZTS: get_persistent_disk_name can return truncated names	2023-11-29 09:34:29 -08:00
commands.cfg	ZTS: Replace MD5 and SHA256 wit XXH128	2024-09-28 09:24:05 -07:00
default.cfg.in	Allowing PERFPOOL to be defined by zfs-test users	2024-02-09 10:02:46 -08:00
libtest.shlib	ZTS: Replace MD5 and SHA256 wit XXH128	2024-09-28 09:24:05 -07:00
math.shlib	Block cloning tests.	2023-12-26 12:01:53 -08:00
properties.shlib	snapdir: add 'disabled' value to make .zfs inaccessible	2024-10-02 09:12:02 -07:00
tunables.cfg	Defer resilver only when progress is above a threshold	2024-10-04 10:41:17 -07:00
zpool_script.shlib	tests: review every awk(1) invocation	2022-04-01 17:57:55 -07:00