If a zfs pool contains a replacing vdev (either created manually by "zpool replace" or by zfsd(8) via autoreplace by physical path) and then new spares get added to the pool, zfsd shouldn't use one to replace the drive that is already being replaced. That's a waste of resources that just slows down the rebuild. PR: 225547 MFC after: 3 weeks Sponsored by: Spectra Logic Corp |
||
---|---|---|
.. | ||
tests | ||
callout.cc | ||
callout.h | ||
case_file.cc | ||
case_file.h | ||
Makefile | ||
Makefile.common | ||
Makefile.depend | ||
vdev_iterator.cc | ||
vdev_iterator.h | ||
vdev.cc | ||
vdev.h | ||
zfsd_event.cc | ||
zfsd_event.h | ||
zfsd_exception.cc | ||
zfsd_exception.h | ||
zfsd_main.cc | ||
zfsd.8 | ||
zfsd.cc | ||
zfsd.h | ||
zpool_list.cc | ||
zpool_list.h |