Fix incorrect usage of volume capabilities #367
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
The capabilities entry for VOL_CAPABILITIES_FORMAT was being used with VOL_CAP_INT_EXCHANGEDATA (so it was actually interpreted as VOL_CAP_FMT_JOURNAL_ACTIVE). Use VOL_CAPABILITIES_INTERFACES instead.
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.
Quick fix for #365, to use the fallback
FSExchangeObjectsEmulateinstead of just failing. Of course it might be nicer to userenamex_npwithRENAME_SWAP, but that is a more complex change. This fix should be applied either way, as long as volume capabilities are still used.