summary refs log tree commit diff stats
path: root/gitlab/issues/target_missing/host_missing/accel_missing/2912.toml
diff options
context:
space:
mode:
Diffstat (limited to 'gitlab/issues/target_missing/host_missing/accel_missing/2912.toml')
-rw-r--r--gitlab/issues/target_missing/host_missing/accel_missing/2912.toml21
1 files changed, 21 insertions, 0 deletions
diff --git a/gitlab/issues/target_missing/host_missing/accel_missing/2912.toml b/gitlab/issues/target_missing/host_missing/accel_missing/2912.toml
new file mode 100644
index 00000000..3e1e1711
--- /dev/null
+++ b/gitlab/issues/target_missing/host_missing/accel_missing/2912.toml
@@ -0,0 +1,21 @@
+id = 2912
+title = "qcow2 image corrupted after snapshot+bitmap action"
+state = "opened"
+created_at = "2025-04-03T10:48:47.619Z"
+closed_at = "n/a"
+labels = ["Storage"]
+url = "https://gitlab.com/qemu-project/qemu/-/issues/2912"
+host-os = "AlmaLinux 9"
+host-arch = "x86_64"
+qemu-version = "qemu-img-9.0.0-10.el9.2.1.x86_64"
+guest-os = "CloudLinux 8"
+guest-arch = "x86"
+description = """When taking a backup of the VM via snapshot + bitmap, the qcow2 image became corrupt:
+`qcow2: Marking image as corrupt: Preventing invalid write on metadata (overlaps with bitmap directory); further corruption events will be suppressed`
+
+This resulted in a corrupt (unfix-able) image (see #2909).
+
+While this process is something that happens multiple times a day, we never hit any issue.
+The underlying storage didn't report any error, so it seems like something inside qemu broke the image."""
+reproduce = """Unfortunately, I was unable to reproduce this issue yet."""
+additional = """"""