Issue/Introduction

This article helps troubleshoot abnormal ZSphere snapshot capacity consumption when snapshot information does not appear in the UI.

Symptoms

• Primary storage or data storage shows abnormal snapshot capacity consumption.
• The UI does not show snapshot information, but the CLI or underlying queries still show multiple snapshots.
• The trigger might include manually deleting a root volume snapshot in a snapshot group.

Environment

• Product: ZVF
• Version: 4.x
• Component: ZSphere
• Affected object: snapshot
• Scenario: For snapshot and backup issues, confirm the current version, deployment type, storage type, and operation timeline.

Possible causes

• The UI displays only snapshot groups or managed snapshot views and does not include individual residual volume snapshots in the underlying system.
• The snapshot group deletion completed only partially, leaving a root volume snapshot or child snapshots.
• Backup, cloning, or manual CLI operations bypassed the UI, causing the management plane snapshot view to differ from the storage-side snapshot view.

Resolution

Perform the following checks in order, and record the affected object, occurrence time, complete error message, and current status.

1. Record the data storage, virtual machine, volume, and snapshot group associated with the capacity anomaly.
2. Query the volume snapshot list through the ZSphere CLI or API, and compare the UI, audit records, and underlying objects.
3. Confirm whether the snapshot is still required by a backup task, cloning task, image creation, or rollback chain.
4. Handle residual snapshots only after contacting ZStack official technical support to confirm the deletion path, backup, and rollback plan. Avoid direct deletion from the underlying system.

Remediation

1. First confirm whether the abnormal snapshot is still required by backup, cloning, image creation, or a rollback chain.
2. Handle residual snapshots only after ZStack official technical support confirms the managed deletion path, backup, and rollback plan.

Verification

• Snapshot information is consistent in the UI, CLI or API, and underlying storage.
• Abnormal capacity consumption is restored, and associated backup, cloning, and rollback functions work normally.