CA-421013: ensure cbt log removed on supporter after disable #786
Conversation
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
When CBT is disabled the CBT log is deleted, on the coordinator, when using shared LVM SRs it is necessary to inform the supporter of this change so that it can remove all information relating to the CBT log volume from the kernel device mapper table. If this is not done a subsequent CBT enable for this VDI will fail if the device mapper table still contains information about the previous, and now deleted, volume. Signed-off-by: Mark Syms <mark.syms@citrix.com>
LunfanZhang
approved these changes
Dec 15, 2025
KevinLCtx
approved these changes
Dec 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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 CBT is disabled the CBT log is deleted, on the coordinator, when using shared LVM SRs it is necessary to inform the supporter of this change so that it can remove all information relating to the CBT log volume from the kernel device mapper table. If this is not done a subsequent CBT enable for this VDI will fail if the device mapper table still contains information about the previous, and now deleted, volume.