sanoid #912: sanoid --prune-snapshots performance boost by removing u… #915
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…nneeded iszfsbusy()
for #912
Option 3) dev/sde/remove-force-prune - If we think the whole functionality is not needed, best would to remove it and keep things more clean. Maybe this could be done in a later version, when experiences shows, that no one ever used --no-force-prune or --double-check-prune. Doing this later probably is too much, but I work in an industry with 20 years warranty periods so I'm used to think this way :)