-
After having tested zfs_autobackup; followed the README and These `busy' systems, in accord with the tutorial here for zfs_autobackup were marked with "zfs set test1". What might be causing them to show busy, and why. Results of attempt to destroy: |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
zfs will show datasets as busy if they have an active hold and you try to delete them. zfs_autobackup uses holds to prevent deleting common snapshots required for incremental transfers. You can use |
Beta Was this translation helpful? Give feedback.
-
Thats correct. I also updated the wiki with this: https://github.com/psy0rz/zfs_autobackup/wiki/Problems#dataset-is-busy |
Beta Was this translation helpful? Give feedback.
zfs will show datasets as busy if they have an active hold and you try to delete them. zfs_autobackup uses holds to prevent deleting common snapshots required for incremental transfers.
You can use
zfs holds path/to/dataset@name-of-the-snapshot
to display the holds for a specific snapshot, andzfs release <tag> path/to/dataset@name-of-the-snapshot
to release such hold. However do note that if you delete the last common snapshot (as marked by the hold), you will be unable to run zfs_autobackup on that dataset without first fully destroying the target dataset.