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

Updated dRAID HOWTO (markdown)

Brian Behlendorf 2019-11-18 16:23:58 -08:00
parent 76b17f701f
commit a3c69a0284
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
dRAID-HOWTO.md

@ -26,7 +26,7 @@ Parity declustering (the fancy term for shuffling drives) has been an active res
# Use dRAID # Use dRAID
First get the code [here](https://github.com/zfsonlinux/zfs/pull/7078), build spl and zfs with _configure --enable-debug_, and install. Then load the zfs kernel module with the following options: First get the code [here](https://github.com/zfsonlinux/zfs/pull/9558), build zfs with _configure --enable-debug_, and install. Then load the zfs kernel module with the following options:
* zfs_vdev_scrub_max_active=10 zfs_vdev_async_write_min_active=4: These options help dRAID rebuild performance. * zfs_vdev_scrub_max_active=10 zfs_vdev_async_write_min_active=4: These options help dRAID rebuild performance.
* draid_debug_lvl=5: This option controls the verbosity level of dRAID debug traces, which is very useful for troubleshooting. * draid_debug_lvl=5: This option controls the verbosity level of dRAID debug traces, which is very useful for troubleshooting.
@ -341,7 +341,7 @@ The dRAID1 vdev in this example shuffles three (4 data + 1 parity) redundancy gr
# Troubleshooting # Troubleshooting
Please report bugs to [the dRAID project](https://github.com/thegreatgazoo/zfs/issues), as long as the code is not merged upstream. The following information would be useful: Please report bugs to [the dRAID PR](https://github.com/zfsonlinux/zfs/pull/9558), as long as the code is not merged upstream. The following information would be useful:
* dRAID configuration, i.e. the *.nvl file created by _draidcfg_ command. * dRAID configuration, i.e. the *.nvl file created by _draidcfg_ command.
* Output of _zpool events -v_ * Output of _zpool events -v_
* dRAID debug traces, which by default goes to _dmesg_ via _printk()_. The dRAID debugging traces can also use _trace_printk()_, which is more preferable but unfortunately GPL only. * dRAID debug traces, which by default goes to _dmesg_ via _printk()_. The dRAID debugging traces can also use _trace_printk()_, which is more preferable but unfortunately GPL only.