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.

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

VM is locked #24

Open
mhand201 opened this issue Mar 3, 2025 · 0 comments
Open

VM is locked #24

mhand201 opened this issue Mar 3, 2025 · 0 comments

Comments

@mhand201
Copy link

mhand201 commented Mar 3, 2025

Hi!

First of all, thank you for your fantastic solution! I would like to share with you the following issue related to automatic snapshots:

The VM enters a locked state due to a snapshot listed in the Proxmox configuration file, even though it does not exist in the volume. Please refer to the two log lines below:

TASK ERROR: VM is locked (snapshot-delete)
TASK ERROR: VM is locked (snapshot-delete)
TASK ERROR: VM is locked (snapshot-delete)
TASK ERROR: VM is locked (snapshot-delete)
TASK ERROR: zfs error: could not find any snapshots to destroy; check snapshot names.

Could you please advise on how to fix this bug? It occurs intermittently.
Could the --force option fix this bug?

To avoid a disk saturation issue, is it possible to add a parameter to check the available disk space as a percentage before launching the snapshots?

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant