Tom Caputi 80a91e7469 Defer new resilvers until the current one ends ... Currently, if a resilver is triggered for any reason while an existing one is running, zfs will immediately restart the existing resilver from the beginning to include the new drive. This causes problems for system administrators when a drive fails while another is already resilvering. In this case, the optimal thing to do to reduce risk of data loss is to wait for the current resilver to end before immediately replacing the second failed drive, which allows the system to operate with two incomplete drives for the minimum amount of time. This patch introduces the resilver_defer feature that essentially does this for the admin without forcing them to wait and monitor the resilver manually. The change requires an on-disk feature since we must mark drives that are part of a deferred resilver in the vdev config to ensure that we do not assume they are done resilvering when an existing resilver completes. Reviewed-by: Matthew Ahrens <mahrens@delphix.com> Reviewed-by: John Kennedy <john.kennedy@delphix.com> Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: @mmaybee Signed-off-by: Tom Caputi <tcaputi@datto.com> Closes #7732		2018-10-18 21:06:18 -07:00
..
linux.run	Defer new resilvers until the current one ends	2018-10-18 21:06:18 -07:00
longevity.run	OpenZFS 9166 - zfs storage pool checkpoint	2018-06-26 10:07:42 -07:00
Makefile.am	Fix "file is executable, but no shebang" warnings	2018-04-06 16:34:21 -07:00
perf-regression.run	OpenZFS 9184 - Add ZFS performance test for fixed blocksize random read/write IO	2018-07-02 13:46:06 -07:00