Fix issue with copy offload index mounts #168
Merged
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
GFS2 Data Movements initiated via the Copy Offload API were not creating index mount directories in the destination. - nnf-dm daemon needs to populate the source storage reference with NnfNodeStorage - nnf-dm index mount check needs to account for NnfNodeStorage types along with NnfStorage types (from copy_in/copy_out directives) Signed-off-by: Blake Devcich <blake.devcich@hpe.com>
roehrich-hpe
approved these changes
Apr 11, 2024
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.
GFS2 Data Movements initiated via the Copy Offload API were not creating
index mount directories in the destination.
NnfNodeStorage
along with NnfStorage types (from copy_in/copy_out directives)
Signed-off-by: Blake Devcich blake.devcich@hpe.com