Probleme mit snapshot commit

shb256

Member
Feb 5, 2022
14
0
6
41
Hallo,

es ist eigentlich kein echtes Proxmox Problem.
Ich habe oVirt zu Proxmox gewechselt. Dort habe ich noch VMs mit Snapshots gehabt. Leider hatte ich die Snapshots dort nicht mehr commited.

Ich habe alle Snapshots, kriege sie aber nicht zusammen.

root@pve:/ldc01# ls -lha
total 15G
drwxr-xr-x 2 root root 4.0K Jun 23 18:49 .
drwxr-xr-x 19 root root 4.0K Jun 23 17:49 ..
-rwxr-xr-x 1 root root 1.8G Jun 23 18:07 267c811d-ad67-4887-9781-d3c8fc85d3f3
-rwxr-xr-x 1 root root 1.0M Jun 23 18:06 267c811d-ad67-4887-9781-d3c8fc85d3f3.lease
-rwxr-xr-x 1 root root 256 Jun 23 18:06 267c811d-ad67-4887-9781-d3c8fc85d3f3.meta
-rwxr-xr-x 1 root root 256K Jun 23 18:40 364f06c5-b9e0-4832-bc2e-4d69fcf95b36
-rwxr-xr-x 1 root root 1.0M Jun 23 18:06 364f06c5-b9e0-4832-bc2e-4d69fcf95b36.lease
-rwxr-xr-x 1 root root 252 Jun 23 18:06 364f06c5-b9e0-4832-bc2e-4d69fcf95b36.meta
-rwxr-xr-x 1 root root 100G Jun 23 18:04 49a16e3c-8942-4a95-a1cb-31e7e71d3461
-rwxr-xr-x 1 root root 1.0M Jun 23 18:04 49a16e3c-8942-4a95-a1cb-31e7e71d3461.lease
-rwxr-xr-x 1 root root 303 Jun 23 18:04 49a16e3c-8942-4a95-a1cb-31e7e71d3461.meta
-rw-r--r-- 1 root root 2.7G Jun 23 18:40 49a16e3c-8942-4a95-a1cb-31e7e71d3461.qcow
-rwxr-xr-x 1 root root 2.4G Jun 23 18:06 c6dc5fb5-d884-42b0-a474-be4a96ee424a
-rwxr-xr-x 1 root root 1.0M Jun 23 18:06 c6dc5fb5-d884-42b0-a474-be4a96ee424a.lease
-rwxr-xr-x 1 root root 256 Jun 23 18:06 c6dc5fb5-d884-42b0-a474-be4a96ee424a.meta
-rwxr-xr-x 1 root root 3.6G Jun 23 18:05 dd9c3a5f-c054-4341-b9f5-f1100dfed132
-rwxr-xr-x 1 root root 1.0M Jun 23 18:05 dd9c3a5f-c054-4341-b9f5-f1100dfed132.lease
-rwxr-xr-x 1 root root 256 Jun 23 18:05 dd9c3a5f-c054-4341-b9f5-f1100dfed132.meta
-rwxr-xr-x 1 root root 1.4G Jun 23 18:05 eb5aaf4d-7947-4add-a017-dd20f9f85598
-rwxr-xr-x 1 root root 1.0M Jun 23 18:05 eb5aaf4d-7947-4add-a017-dd20f9f85598.lease
-rwxr-xr-x 1 root root 256 Jun 23 18:05 eb5aaf4d-7947-4add-a017-dd20f9f85598.meta
root@pve:/ldc01# qemu-img info --backing-chain 364f06c5-b9e0-4832-bc2e-4d69fcf95b36
image: 364f06c5-b9e0-4832-bc2e-4d69fcf95b36
file format: qcow2
virtual size: 100 GiB (107374182400 bytes)
disk size: 260 KiB
cluster_size: 65536
backing file: 267c811d-ad67-4887-9781-d3c8fc85d3f3
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false

image: 267c811d-ad67-4887-9781-d3c8fc85d3f3
file format: qcow2
virtual size: 100 GiB (107374182400 bytes)
disk size: 1.68 GiB
cluster_size: 65536
backing file: c6dc5fb5-d884-42b0-a474-be4a96ee424a
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false

image: c6dc5fb5-d884-42b0-a474-be4a96ee424a
file format: qcow2
virtual size: 100 GiB (107374182400 bytes)
disk size: 2.38 GiB
cluster_size: 65536
backing file: dd9c3a5f-c054-4341-b9f5-f1100dfed132
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false

image: dd9c3a5f-c054-4341-b9f5-f1100dfed132
file format: qcow2
virtual size: 100 GiB (107374182400 bytes)
disk size: 3.55 GiB
cluster_size: 65536
backing file: eb5aaf4d-7947-4add-a017-dd20f9f85598
backing file format: qcow2
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false

image: eb5aaf4d-7947-4add-a017-dd20f9f85598
file format: qcow2
virtual size: 100 GiB (107374182400 bytes)
disk size: 1.3 GiB
cluster_size: 65536
backing file: 49a16e3c-8942-4a95-a1cb-31e7e71d3461
backing file format: raw
Format specific information:
compat: 1.1
compression type: zlib
lazy refcounts: false
refcount bits: 16
corrupt: false
extended l2: false

image: 49a16e3c-8942-4a95-a1cb-31e7e71d3461
file format: raw
virtual size: 100 GiB (107374182400 bytes)
disk size: 2.54 GiB
root@pve:/ldc01# qemu-img commit 364f06c5-b9e0-4832-bc2e-4d69fcf95b36
Image committed.
root@pve:/ldc01#
Nach dem Commit sollten ja alle Daten im 49... drin sein.
Wenn ich dann das file 49... importiere habe, habe ich den stand von 49... vor dem Commit, hat jemand eine Idee für mich?
Ich meine, dass ich das genau so schon gemacht habe. macht es einen unterschied, ob das base file ein RAW oder qcow ist?

Danke für eure Hilfe

SHB
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!