From 266a95c3ca6f16db690a0394e146ebaa52fc913c Mon Sep 17 00:00:00 2001 From: DatuX Date: Thu, 28 Apr 2022 15:56:05 +0200 Subject: [PATCH] Updated Problems (markdown) --- Problems.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/Problems.md b/Problems.md index 3cc2e92..695d5e6 100644 --- a/Problems.md +++ b/Problems.md @@ -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