Updated Problems (markdown)

DatuX
2022-04-28 15:56:05 +02:00
parent c2bd6f493e
commit 266a95c3ca

@ -32,6 +32,16 @@ Try using the --ignore-transfer-errors option. This will ignore the error. It wi
This happens if you forget to use --encrypt, while the target datasets are already encrypted. (Very strange error message indeed)
## "dataset is busy"
If you try to destroy a snapshot and it busy, there might be multiple reasons, but dont forget to check if the snapshot has holds with:
> zfs holds `zpool/fs1@snapshot1`
Release it with zfs release.
Use --no-holds in zfs-autobackup if you dont want to use holds.
## Other problems
Feel free to ask questions about zfs-autobackup on our issue tracker at https://github.com/psy0rz/zfs_autobackup/issues