correcting lastsnapsent when resuming broken sending#163
Open
bassilov wants to merge 2 commits intobolthole:masterfrom
Open
correcting lastsnapsent when resuming broken sending#163bassilov wants to merge 2 commits intobolthole:masterfrom
bassilov wants to merge 2 commits intobolthole:masterfrom
Conversation
Member
|
Hello, You make some surprisng statements, about last snaps, and also using awk print $2, which doesnt make sense to me. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When resuming broken sending the last succesful snap will be different than the one made for sync if there are intermediate snaps and the sync process was interrupted while sending not zrep snap.
So my patch fixes it.
It does not fix the problem when sync process was interrupted during sending nested zfs.
I use -s option only for single zfs