Archive-Team
/
zfs
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 103 Wiki Activity

Updated dRAID HOWTO (markdown)

Isaac Huang 2017-03-09 21:43:01 -07:00
parent 403d49de85
commit 991a475916
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
dRAID-HOWTO.md

@ -288,6 +288,12 @@ The sequential rebuild process also works for the mirror vdev. Currently it's en
Later it will be changed to use resilver by default, and rebuild only if the user explicitly requests so. Later it will be changed to use resilver by default, and rebuild only if the user explicitly requests so.
### Rebuild throttling
The rebuild process may delay _zio_ according to the ZFS options _zfs_scan_idle_ and _zfs_resilver_delay_, which are the same options used by resilver. Moreover, when a dRAID vdev has lost all redundancy, e.g. a draid2 with 2 faulted child drives, the rebuild process will go faster by reducing the delay to _zfs_resilver_delay/2_ because the vdev is now in critical state.
After delaying, the rebuild zio is issued using priority _ZIO_PRIORITY_SCRUB_ for reads and _ZIO_PRIORITY_ASYNC_WRITE_ for writes. Therefore the options that control the queuing of these two IO priorities will affect rebuild _zio_ as well, for example _zfs_vdev_scrub_min_active_, _zfs_vdev_scrub_max_active_, _zfs_vdev_async_write_min_active_, and _zfs_vdev_async_write_max_active_.
## Rebalance ## Rebalance
Distributed spare space can be made available again by simply replacing any failed drive with a new drive. This process is called _rebalance_ which is essentially a _resilver_: Distributed spare space can be made available again by simply replacing any failed drive with a new drive. This process is called _rebalance_ which is essentially a _resilver_: