summary refs log tree commit diff stats
path: root/results/scraper/launchpad-without-comments/1289898
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:24:58 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:27:06 +0000
commit33606b41d35115f887ea688b1a16f2ff85bf2fe4 (patch)
tree406b2c7b19a087ba437c68f3dbf0b589fa1d6150 /results/scraper/launchpad-without-comments/1289898
parentadedf8771bc4de3113041ca21bd4d0d1c0014b6a (diff)
downloademulator-bug-study-33606b41d35115f887ea688b1a16f2ff85bf2fe4.tar.gz
emulator-bug-study-33606b41d35115f887ea688b1a16f2ff85bf2fe4.zip
add launchpad bug reports without comments
Diffstat (limited to 'results/scraper/launchpad-without-comments/1289898')
-rw-r--r--results/scraper/launchpad-without-comments/12898987
1 files changed, 7 insertions, 0 deletions
diff --git a/results/scraper/launchpad-without-comments/1289898 b/results/scraper/launchpad-without-comments/1289898
new file mode 100644
index 00000000..6b3911a8
--- /dev/null
+++ b/results/scraper/launchpad-without-comments/1289898
@@ -0,0 +1,7 @@
+qemu-system-ppc64 easily cause file corruption
+
+the qemu-system-ppc64 is used to run Fedora-19 on RHEL 5.3.
+Previously I was using QEMU 1.5.x for several months with no problem. But after the RHEL 5.3 host damaged, and rebuilt, now I tried both QEMU 1.6.2 and QEMU 1.7.0, found both can easily cause file corruptions. Symptoms:
+
+* using scp to transfer a tar.bz file from the RHEL 5.3 host to the Fedora-19 PPC VM, found the size is correct, but the content is corrupted from the middle of the 80+ MB file.  re-transfer again, got a correct file. But after untar, found some extracted files corrupted.
+The extracted file corruption happened several times, and also the filesystem in the VM had corrupted several times, had to restore the boot image to recover.
\ No newline at end of file