Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

lvm vgremove --force is not enough sometimes #127

Closed
raharper opened this issue Apr 5, 2023 · 1 comment
Closed

lvm vgremove --force is not enough sometimes #127

raharper opened this issue Apr 5, 2023 · 1 comment

Comments

@raharper
Copy link
Collaborator

raharper commented Apr 5, 2023

On a system with a damaged ThinPool LV, the RemoveVG() call will invoke lvm vgremove --force <lv> and this command returns 5, and mentioning that there is a thin pool transaction_id mismatch.

Adding an extra '--force' to the command will more forcefully remove the vg, with more warnings in the output.
@smoser
Copy link
Collaborator

smoser commented Jan 12, 2024

I'm pretty sure this was fixed by #129.
reopen if that is wrong.

@smoser smoser closed this as completed Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@smoser @raharper