Implement DESTROY_AFTER optional argument for bin/zfs-auto-snapshot. #44
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lytboris
force-pushed
the
destroy-after
branch
3 times, most recently
from
ec0a212
to
9a5b80b
Compare
lytboris
changed the title
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
zfs-auto-snapshot can be used to create upon-boot snapshots so one can debug any startup issues that are overwritten by services startup process.
The downside of using zfs-auto-snapshot for such purpose is that these snapshots stays forever on a well-performing server (which does not require to be rebooted).
This patch introduces support for a custom optional attribute that is set on a snapshots and specifies timestamp when it should be deleted not related to number of snapshots.