You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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!
The text was updated successfully, but these errors were encountered: