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
..
callbacks	Split functional testings via github action matrix	2023-03-15 10:41:05 -07:00
cmd	ZTS: increase timeout of mmap_sync_001_pos	2024-09-17 12:03:08 -07:00
include	Defer resilver only when progress is above a threshold	2024-10-04 10:41:17 -07:00
tests	Defer resilver only when progress is above a threshold	2024-10-04 10:41:17 -07:00
.gitignore	autoconf: use include directives instead of recursing down cmd	2022-05-10 10:18:38 -07:00
Makefile.am	tests: add test for vdev_disk page alignment check	2024-04-11 14:42:46 -07:00