fix(clone): setting properties on the clone volume #57
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
Signed-off-by: Pawan <pawan@mayadata.io>
kmova
reviewed
Mar 11, 2020
kmova
approved these changes
Mar 12, 2020
This was referenced Mar 12, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
fixes #55.
When we clone the zvol, it inherits volsize and block size from the snapshot from which this clone is created. This is not true for datasets, we have to set all the properties while creating the clone. Also, properties like compression, dedup will not be set on the cloned volume for both zvol and dataset. Here I am setting all the prperties for zvol and dataset while creating the clone volume.
Signed-off-by: Pawan pawan@mayadata.io