Repository navigation
Add workaround for lvmcluster pool removal - #3369
Merged
Merged
Conversation
presztak
changed the title
Before removing a shared VG, perform lockstop and change the VG lock type to `none`. This avoids relying on lvmlockd/sanlock during VG removal. In lvmlockd 2.03.31(2) (2025-02-27), VG removal may fail due to an inconsistent state between sanlock and lvmlockd, resulting in lock-related errors. Signed-off-by: Piotr Resztak <piotr.resztak@futurfusion.io>
presztak
force-pushed
the
fix_lvmcluster_delete
branch
from
May 20, 2026 16:20
cb12a11 to
a05163c
Compare
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
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.
Before removing a shared VG, perform
lockstopand change the VG lock type tonone. This avoids relying on lvmlockd/sanlock during VG removal.In lvmlockd 2.03.31(2) (2025-02-27), VG removal may fail due to an inconsistent state between sanlock and lvmlockd, resulting in lock-related errors.
Closes: #3342