Volume Stuck in Snapshotting

[boubouX]

Hello,

I have a volume stuck in ”Snapshotting” for several days.

This volume also has a daily snapshot schedule, which I would like to delete, but the WebUI does not offer me that option, likely due to the “Snapshotting” status.

I have removed all my other scheduled volume snapshots; now, I see only one entry in the snapshot_schedule and snapshot_policy tables.

Can I delete this record from both tables?

I also found the entry in the snapshot_view table.

This is a 24/7 VM with heavy usage, and I cannot shut it down for another two days.

Does anyone have any suggestions for a resolution?

Thank you,
Antoine

[prashanthr2]

@boubouX I wouldn't make changes to DB unless it's absolutely necessary and there is no other way.

If volume is stuck in snapshotting, I think you should try to fix this first and do a clean delete of the snapshot schedule from WebUI. Do you know if why this happened and everything looks good with the volume from hypervisor end? Also, what is the hypervisor here?

[boubouX]

Hello prashanthr2,

Thank you for your response.

My best guess is that the issue occurred because the account or domain temporarily ran out of secondary storage capacity quota, which has since been resolved.

Here is the current status:

1. The VM is working as expected.
2. A snapshot of its volume is in the Creating state, with a DAILY interval type, created on October 19.
3. The VDI is 250 GB, stored locally on the KVM host in QCOW2 format. It is not shown as snapshotted when checked via qemu-img info.
4. A manual reverse database lookup from the VDI path returns the unexpected VM name “ABTWDCAPP01” instead of the expected “TS02”. “ABTWDCAPP01” does not appear in the web UI.
5. In the web UI, the volume state is “Snapshotting.” It shows no metrics collected, which is unusual, and a SNAPSHOT.CREATED event is logged every 5 minutes.
6. Every 5 minutes, the Management Server logs the following error:

2025-10-28 06:35:24,718 ERROR [c.c.s.s.SnapshotSchedulerImpl] (SnapshotPollTask:ctx-7fdc17a1) (logid:d13be60e) The scheduling of snapshot [6763e09b-dd3b-4ff4-b1fd-1046d0dbb681] for volume [147] failed due to [com.cloud.exception.InvalidParameterValueException: VolumeId: 147 is not in Ready state but Snapshotting. Cannot take snapshot.].

7. The environment is running Apache CloudStack 4.19.3, and the Management Server was last rebooted about a day ago.
8. I can shut down the VM in about 16 hours for further investigation.

Do you have any suggestions for the next steps?

Best regards

[prashanthr2]

Hello @boubouX Thanks for details on the issue.

Since you can stop the VM in next few hours I would recommend the following

1. Stop the VM and check if the state of the Volume changes to Ready (TBH I doubt if this happens)
2. If the volume remains in Snapshotting state. Update the DB to reflect the state of the affected VM to Ready. Once done you should be able to cancel the snapshot schedule from Web interface.

Note: Please take the backup of your DB before making any changes.