We have a new HVM cluster installed at a customer. Now we want to implement Parallels RAS but are running into some problems with the versioning. We use the custom provider in RAS and that works for connecting with the HPE Morpheus VM Essentials manager, creating a template and enroll hosts. But when we add a new version to the template VME cannot enroll the hosts anymore because of a mismatch in the new of the qcow file that is used to create the clone. I did a lot off troubleshouting below the finding.
Can some help me with this, if there is beta testing needed that's no problem we also have a test cluster for this.
VM Essentials clone failure: copy-for-backup naming mismatch
Product / Environment
- Product: HPE Morpheus VM Essentials (VME)
- VME version: 9.01
- Cluster / node(s) affected: hvm-host02
- Datastore: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE
- Template instance: MASTERIMAGE (disk: hvm_4-disk-0-dab79d2)
- Access method: Morpheus REST API (/api/instances), used via a custom automation integration (Parallels RAS Custom Provider)
API calls used by the automation (for context)
To rule out that this is caused by how the automation drives the API, this section lists the exact and complete set of REST calls involved in the revert-then-deploy flow. There are only two calls, both simple, documented Morpheus endpoints:
- Revert to the desired template version:
- PUT /api/instances/{id}/revert-snapshot/{snapshotId}
{snapshotId} is resolved beforehand via GET /api/instances/{id}/snapshots, matching on the snapshot name that corresponds to the desired template version.
- Deploy/clone a new instance from the (now-reverted) template:
- PUT /api/instances/{id}/clone
- Body: { "name": "<new-instance-name>" }
No other API call is made in between, and no parameter exists on either endpoint to specify, influence, or override which backing/backup file the clone operation should read from — the /clone request body only accepts the new instance name. The resolution of the copy-for-backup source file (and the naming mismatch described below) therefore happens entirely server-side, inside VME's own handling of the /clone request, after the automation's request has already been sent. The automation has no visibility into this step and no way to influence, detect, or correct it through the documented API surface — it only observes the eventual success/failure status via the same /clone task polling used for any other clone operation.
Summary
Deploying (cloning) a new VM from a template instance reliably fails at the "Deploy Virtual Machine" step with:
Failed to create server volumes: Failed to clone volume: cp: cannot stat
'/mnt/<datastore-uuid>/MASTERIMAGE/hvm_4-disk-0-dab79d2-copy-for-backup':
No such file or directory
The deploy process looks up a copy-for-backup disk file using only the base disk name (<base-disk-name>-copy-for-backup). The file that is actually created on disk is always named after the most recent snapshot instead: <base-disk-name>-snap-<timestamp>-copy-for-backup. Because the base-name file is never created, the lookup fails every time.
This has been reproduced consistently across three separate test runs: with 1 snapshot in the chain, with 2 snapshots in the chain, and during a parallel deployment of 2 instances from the same template. In every case the deploy fails with the identical error, at the identical path pattern.
We have used qemu-img info --backing-chain to independently verify the content of the copy-for-backup files that are created (see Evidence below). The backing-chain references and file sizes are correct in every case — each copy-for-backup file correctly backs onto the intended parent snapshot layer with matching data. This confirms the issue is isolated to the filename lookup/resolution step, not to the underlying disk-cloning logic — the correct data is being prepared, it is simply never found by the process that consumes it.
Steps to reproduce
- Provision a template instance and take a snapshot (any single version is sufficient to reproduce — a multi-snapshot chain is not required).
- Deploy/clone a new instance from the template via PUT /api/instances/{id}/clone.
- Deployment fails at "Deploy Virtual Machine" (observed duration ~3–9s) with the error shown above.
- Filesystem inspection at the time of failure shows a correctly-formed <base-disk-name>-snap-<timestamp>-copy-for-backup file exists, but no file named <base-disk-name>-copy-for-backup exists or is ever created.
Expected behavior
The clone/deploy process should resolve the copy-for-backup file that corresponds to the current top of the snapshot chain (i.e. the same file it itself just created), rather than looking up a fixed base-disk-name-only path that is never populated once a template has any snapshot.
Evidence — timeline and backing-chain verification
Monitoring was done with a custom polling watcher (qemu-img info --backing-chain run against every newly-created file matching the template's disk ID). Three consecutive test runs, summarized:
Test 1 — single snapshot:
09:35:xx CREATE hvm_4-disk-0-dab79d2-snap-1787816186686
backing file: hvm_4-disk-0-dab79d2 (base, 22 GiB)
09:37:01 CREATE hvm_4-disk-0-dab79d2-snap-1787816186686-copy-for-backup
backing file: hvm_4-disk-0-dab79d2 (base, 22 GiB) -- matches original
09:37:xx Deploy Virtual Machine fails (9s) — see HISTORY DETAIL screenshot
Test 2 — second snapshot added:
09:46:57 CREATE hvm_4-disk-0-dab79d2-snap-1787903217019
backing file: hvm_4-disk-0-dab79d2 (base)
09:52:37 CREATE hvm_4-disk-0-dab79d2-snap-1787903217019-copy-for-backup
backing file: hvm_4-disk-0-dab79d2 (base) -- matches original, same size (428 MiB)
09:57:26 CREATE hvm_4-disk-0-dab79d2-snap-1787903845631
backing file: hvm_4-disk-0-dab79d2-snap-1787903217019
10:00:01 CREATE hvm_4-disk-0-dab79d2-snap-1787903845631-copy-for-backup
backing file: hvm_4-disk-0-dab79d2-snap-1787903217019 -- matches original, same size (200 KiB)
10:00:xx Deploy Virtual Machine fails (3s) — identical error, identical path
'.../hvm_4-disk-0-dab79d2-copy-for-backup': No such file or directory
In both tests, every copy-for-backup file's backing-chain reference and disk size exactly matches its corresponding original snapshot file — confirming correct data preparation. Only the final lookup (against the non-existent base-name path) fails.
Note: a Failed to get shared "write" lock message was observed once during monitoring — this was caused by our own read-only monitoring command colliding with VME's own active write lock on the file, not a VME-side error.
Test 3 — parallel deployment of 2 instances, same result: two independent snapshot/copy-for-backup creation sequences ran concurrently (one per instance being deployed), each followed by the same deploy failure at the same base-name lookup path. This confirms the issue is not related to sequencing or timing of a single deploy, but is a deterministic lookup defect that occurs on every deploy regardless of snapshot count or concurrency.
Workaround currently applied (manual, not sustainable)
Manually creating/hardlinking a file named <base-disk-name>-copy-for-backup that points to the most recent <base-disk-name>-snap-<timestamp>-copy-for-backup file allows the deploy to succeed:
cd /mnt/<datastore-uuid>/MASTERIMAGE/
sudo cp hvm_4-disk-0-dab79d2-snap-<latest-timestamp>-copy-for-backup \
hvm_4-disk-0-dab79d2-copy-for-backup
This requires direct shell/SSH access to the appliance and is not supportable for automated, API-driven provisioning workflows (Parallels RAS Custom Provider / Morpheus REST API), since the REST API surface gives no way to influence or correct this internal filename resolution.
Impact
- No template with an existing snapshot can be reliably cloned/deployed from without manual filesystem intervention — this affects every template-based deployment, not only multi-version templates.
- Automated provisioning through the Morpheus REST API cannot work around this, since the naming logic sits below the API layer, in the appliance's internal disk-clone handling.
- Orphaned -copy-for-backup files can accumulate on the datastore when deploy attempts fail before reaching cleanup, consuming additional disk space over time.
Question for HPE Support
- Is this a known defect in the copy-for-backup filename resolution used by the instance clone/deploy process?
- Is there a supported way (API-level or configuration-level) to make the deploy process resolve the copy-for-backup file it actually created, instead of a fixed base-disk-name path?
- Is there a supported cleanup procedure for orphaned -copy-for-backup files left behind by failed deploy attempts?
Attachments below
- Screenshot: HISTORY DETAIL dialog, Test01-003, 08/28/2026 09:37 AM, Status: failed, error referencing snapshot v1 test
- Screenshot: HISTORY DETAIL dialog, Test01-003, 08/28/2026 10:00 AM, Status: failed, identical error pattern, second/parallel test
- Full monitoring logs (timestamped qemu-img info --backing-chain output for every created/deleted file) for both test runs — available on request, confirm correct backing-chain data at every step
sudo ./copy-for-backup-pollwatch.sh /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE
# Log gestart: 2026-08-28 09:46:26
# Watching (polling elke 1s): /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE
----
Stop met Ctrl+C zodra de deploy klaar is (geslaagd of gefaald).
----
[2026-08-28 09:46:26] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 116 MiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686
protocol type: file
file length: 117 MiB (122486784 bytes)
disk size: 116 MiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 09:46:27] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686-copy-for-backup
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686-copy-for-backup
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 116 MiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686-copy-for-backup
protocol type: file
file length: 117 MiB (122486784 bytes)
disk size: 116 MiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 09:46:57] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 200 KiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
protocol type: file
file length: 194 KiB (199168 bytes)
disk size: 200 KiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 09:46:58] DELETE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686
----
[2026-08-28 09:50:39] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686-copy-for-backup
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686-copy-for-backup
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 116 MiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686-copy-for-backup
protocol type: file
file length: 117 MiB (122486784 bytes)
disk size: 116 MiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 09:50:40] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 09:50:41] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
----
[2026-08-28 09:52:36] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686-copy-for-backup
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686-copy-for-backup
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 116 MiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686-copy-for-backup
protocol type: file
file length: 117 MiB (122486784 bytes)
disk size: 116 MiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 09:52:37] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 09:52:38] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 152 MiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
protocol type: file
file length: 152 MiB (159907840 bytes)
disk size: 152 MiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 09:57:26] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 200 KiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631
protocol type: file
file length: 194 KiB (199168 bytes)
disk size: 200 KiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 428 MiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
protocol type: file
file length: 429 MiB (449445888 bytes)
disk size: 428 MiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 09:59:59] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631-copy-for-backup
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631-copy-for-backup
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 200 KiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631-copy-for-backup
protocol type: file
file length: 194 KiB (199168 bytes)
disk size: 200 KiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 428 MiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
protocol type: file
file length: 429 MiB (449445888 bytes)
disk size: 428 MiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 10:00:01] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019-copy-for-backup
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019-copy-for-backup
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 428 MiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019-copy-for-backup
protocol type: file
file length: 429 MiB (449445888 bytes)
disk size: 428 MiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 10:00:04] DELETE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631-copy-for-backup
----
[2026-08-28 10:00:38] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631-copy-for-backup
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631-copy-for-backup
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 200 KiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019-copy-for-backup
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631-copy-for-backup
protocol type: file
file length: 194 KiB (199168 bytes)
disk size: 200 KiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019-copy-for-backup
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 428 MiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019-copy-for-backup
protocol type: file
file length: 429 MiB (449445888 bytes)
disk size: 428 MiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 10:00:40] DELETE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631-copy-for-backupsudo ./copy-for-backup-pollwatch.sh /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE
# Log gestart: 2026-08-28 09:46:26
# Watching (polling elke 1s): /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE
----
Stop met Ctrl+C zodra de deploy klaar is (geslaagd of gefaald).
----
[2026-08-28 09:46:26] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 116 MiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686
protocol type: file
file length: 117 MiB (122486784 bytes)
disk size: 116 MiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 09:46:27] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686-copy-for-backup
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686-copy-for-backup
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 116 MiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686-copy-for-backup
protocol type: file
file length: 117 MiB (122486784 bytes)
disk size: 116 MiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 09:46:57] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 200 KiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
protocol type: file
file length: 194 KiB (199168 bytes)
disk size: 200 KiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 09:46:58] DELETE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686
----
[2026-08-28 09:50:39] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686-copy-for-backup
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686-copy-for-backup
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 116 MiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686-copy-for-backup
protocol type: file
file length: 117 MiB (122486784 bytes)
disk size: 116 MiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 09:50:40] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 09:50:41] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
----
[2026-08-28 09:52:36] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686-copy-for-backup
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686-copy-for-backup
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 116 MiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787816186686-copy-for-backup
protocol type: file
file length: 117 MiB (122486784 bytes)
disk size: 116 MiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 09:52:37] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 09:52:38] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 152 MiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
protocol type: file
file length: 152 MiB (159907840 bytes)
disk size: 152 MiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 09:57:26] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 200 KiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631
protocol type: file
file length: 194 KiB (199168 bytes)
disk size: 200 KiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 428 MiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
protocol type: file
file length: 429 MiB (449445888 bytes)
disk size: 428 MiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 09:59:59] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631-copy-for-backup
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631-copy-for-backup
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 200 KiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631-copy-for-backup
protocol type: file
file length: 194 KiB (199168 bytes)
disk size: 200 KiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 428 MiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019
protocol type: file
file length: 429 MiB (449445888 bytes)
disk size: 428 MiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 10:00:01] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019-copy-for-backup
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019-copy-for-backup
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 428 MiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019-copy-for-backup
protocol type: file
file length: 429 MiB (449445888 bytes)
disk size: 428 MiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 10:00:04] DELETE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631-copy-for-backup
----
[2026-08-28 10:00:38] CREATE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631-copy-for-backup
Backing-chain op dit moment:
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631-copy-for-backup
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 200 KiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019-copy-for-backup
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631-copy-for-backup
protocol type: file
file length: 194 KiB (199168 bytes)
disk size: 200 KiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019-copy-for-backup
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 428 MiB
cluster_size: 65536
backing file: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903217019-copy-for-backup
protocol type: file
file length: 429 MiB (449445888 bytes)
disk size: 428 MiB
image: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
file format: qcow2
virtual size: 160 GiB (171798691840 bytes)
disk size: 22 GiB
cluster_size: 131072
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false
Child node '/file':
filename: /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2
protocol type: file
file length: 23.1 GiB (24759369728 bytes)
disk size: 22 GiB
----
[2026-08-28 10:00:40] DELETE -> /mnt/2fef544e-28d9-40ff-9419-c1f141fcadd2/MASTERIMAGE/hvm_4-disk-0-dab79d2-snap-1787903845631-copy-for-backup