diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-05-30 16:52:07 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-05-30 16:52:17 +0200 |
| commit | 9260319e7411ff8281700a532caa436f40120ec4 (patch) | |
| tree | 2f6bfe5f3458dd49d328d3a9eb508595450adec0 /gitlab/issues/target_missing/host_missing/accel_missing/2649.toml | |
| parent | 225caa38269323af1bfc2daadff5ec8bd930747f (diff) | |
| download | qemu-analysis-9260319e7411ff8281700a532caa436f40120ec4.tar.gz qemu-analysis-9260319e7411ff8281700a532caa436f40120ec4.zip | |
gitlab scraper: download in toml and text format
Diffstat (limited to 'gitlab/issues/target_missing/host_missing/accel_missing/2649.toml')
| -rw-r--r-- | gitlab/issues/target_missing/host_missing/accel_missing/2649.toml | 50 |
1 files changed, 0 insertions, 50 deletions
diff --git a/gitlab/issues/target_missing/host_missing/accel_missing/2649.toml b/gitlab/issues/target_missing/host_missing/accel_missing/2649.toml deleted file mode 100644 index 81db945c6..000000000 --- a/gitlab/issues/target_missing/host_missing/accel_missing/2649.toml +++ /dev/null @@ -1,50 +0,0 @@ -id = 2649 -title = "Data corruption with qcow2 images" -state = "closed" -created_at = "2024-11-03T18:27:20.732Z" -closed_at = "2024-11-10T07:36:24.221Z" -labels = [] -url = "https://gitlab.com/qemu-project/qemu/-/issues/2649" -host-os = "Arch Linux" -host-arch = "x86_64" -qemu-version = "9.1.1-1" -guest-os = "n/a" -guest-arch = "n/a" -description = "n/a" -reproduce = """``` -# Create an example file with old version of qemu-img and fill it with random data. -$ qemu-img-8.2.2 create -f qcow2 file.qcow2 600000000000 -$ qemu-nbd-8.2.2 -c /dev/nbd0 file.qcow2 -$ dd if=/dev/random of=/dev/nbd0 bs=1000000 count=600000 -$ qemu-nbd-8.2.2 -d /dev/nbd0 -/dev/nbd0 disconnected - -# Get the correct checksum of both qcow2 file and its contents -$ sha256sum -b file.qcow2 -ca471f6822af4fcf3c81bc5cc671493be06a837b71b43c1f747042759da587b9 *file.qcow2 -$ qemu-nbd-8.2.2 -r -c /dev/nbd0 file.qcow2 -$ sha256sum -b /dev/nbd0 -5dac11e88f891740da3b655588b2e62037962d1ba6377efce30124d6224dd0d1 */dev/nbd0 -$ qemu-nbd-8.2.2 -d /dev/nbd0 -/dev/nbd0 disconnected - -# Use the qcow2 file with new version. -# We're using qemu-nbd here, but the same happens when qcow2 is attached to a guest -# running in the new version qemu-system-86_64-9.1.1 and can be seen through guest's -# /dev/vda. -# Note that the checksum is different than before, and also non-deterministic -# (running sha256sum twice produces different results even though the file is -# read-only and hasn't changed). -$ sha256sum -b file.qcow2 -ca471f6822af4fcf3c81bc5cc671493be06a837b71b43c1f747042759da587b9 *file.qcow2 -$ qemu-nbd-9.1.1 -r -c /dev/nbd0 file.qcow2 -$ sha256sum -b /dev/nbd0 -1793a38b9b964d3fc643629284722373e9d5dedea68e35900ace777b57688926 */dev/nbd0 -$ sha256sum -b /dev/nbd0 -98f900f9cd174493d0bfcf06e2bc86f5ee99dfa04c90d6832fa941e384b62d49 */dev/nbd0 -$ qemu-nbd-9.1.1 -d /dev/nbd0 -/dev/nbd0 disconnected -$ sha256sum -b file.qcow2 -ca471f6822af4fcf3c81bc5cc671493be06a837b71b43c1f747042759da587b9 *file.qcow2 -```""" -additional = """No errors in either host or guest logs. When using a qcow2 with an actual filesystem, you may see reports of corruption from the filesystem driver.""" |