We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The backend throws an error when zfs destroy(delete) pool/dataset exits non-zero if they are child snapshots.
Fix seems trivial, but should we:
add the -r switch to Dataset->destroy(), or
Catch the error if destroy exits non-zero
Comments?
The text was updated successfully, but these errors were encountered:
Sorry, forgot to mention. When this happens the mntent is also removed from database, that's the main problem
Sorry, something went wrong.
I think if the error in child snapshots that can not be deleted without -r option, user should be asked with a dialog for deletion.
-r
nicjo814
subzero79
luxflow
No branches or pull requests
The backend throws an error when zfs destroy(delete) pool/dataset exits non-zero if they are child snapshots.
Fix seems trivial, but should we:
add the -r switch to Dataset->destroy(), or
Catch the error if destroy exits non-zero
Comments?
The text was updated successfully, but these errors were encountered: