1 files changed, 48 insertions, 0 deletions
diff --git a/results/classifier/118/graphic/2909 b/results/classifier/118/graphic/2909
new file mode 100644
index 000000000..ca0fd29ff
--- /dev/null
+++ b/results/classifier/118/graphic/2909
@@ -0,0 +1,48 @@
+graphic: 0.888
+device: 0.830
+ppc: 0.626
+mistranslation: 0.618
+semantic: 0.592
+performance: 0.469
+register: 0.468
+hypervisor: 0.458
+vnc: 0.417
+assembly: 0.412
+debug: 0.400
+i386: 0.393
+risc-v: 0.366
+PID: 0.365
+virtual: 0.361
+VMM: 0.356
+x86: 0.349
+KVM: 0.344
+boot: 0.336
+architecture: 0.321
+permissions: 0.314
+socket: 0.273
+kernel: 0.267
+arm: 0.225
+TCG: 0.215
+user-level: 0.198
+peripherals: 0.168
+network: 0.167
+files: 0.042
+
+Corrupt qcow2 images with broken bitmap unfixable
+Description of problem:
+During a backup of a VM (via bitmaps), the disk of the VM/Snapshot went out of space.
+The VM was stopped, leaving the image in a bad state.
+
+But now when trying to repair it, it was stuck:
+```
+# qemu-img check -r all /dev/mapper/e1d2ff33--c3fd--4c1a--bcd1--2047e4efc362-efbd8056--720a--47b6--bede--4325d576ffb9
+qemu-img: Could not open '/dev/mapper/e1d2ff33--c3fd--4c1a--bcd1--2047e4efc362-efbd8056--720a--47b6--bede--4325d576ffb9': Bitmap '' doesn't satisfy the constraints
+```
+
+But if you want to remove the bitmap:
+```
+# qemu-img bitmap --remove /dev/mapper/e1d2ff33--c3fd--4c1a--bcd1--2047e4efc362-efbd8056--720a--47b6--bede--4325d576ffb9 ''
+qemu-img: Could not open '/dev/mapper/e1d2ff33--c3fd--4c1a--bcd1--2047e4efc362-efbd8056--720a--47b6--bede--4325d576ffb9': qcow2: Image is corrupt; cannot be opened read/write
+```
+
+It seems like qemu-img check needs some option to clear invalid bitmaps. So the image can be repaired including dropping the invalid bitmap.