Add link to "dataset is busy" wiki page

Home.md

@@ -305,7 +305,7 @@ To prevent confusion, and to be more flexible, I would advise you to always use
 * Use these only one time if needed: `--force` `--destroy-incompatible` `--rollback`. Don't add them to your script. Try to solve the underlying cause if you keep needing them.
 * Set the ```readonly``` property of the target filesystem to ```on```. This prevents changes on the target side. (Due to the nature of ZFS itself, if any changes are made to a dataset on the target machine, then the next backup to that target machine will probably fail. Such a failure can probably be resolved by perfroming a target-side zfs rollback of the affected dataset.) Note that ```readonly``` prevents changes to the CONTENTS of the dataset directly. It's still possible to receive new datasets and manipulate properties etc.
 * Use ```--clear-refreservation``` to save space on your backup machine.
-* zfs-autobackup uses holds by default, so you might get "dataset busy" if you try to destroy a snapshot. (check zfs holds --help)
+* zfs-autobackup uses holds by default, so you might get "dataset busy" if you try to destroy a snapshot. (check zfs holds --help or see [https://github.com/psy0rz/zfs_autobackup/wiki/Problems#dataset-is-busy](here.)
 
 ## Restore example