From: Peter Lieven <pl@kamp.de>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: qemu-stable@nongnu.org
Subject: [Qemu-devel] Data corruption in Qemu 2.7.1
Date: Fri, 13 Jan 2017 11:44:32 +0100 [thread overview]
Message-ID: <5878AF90.8020709@kamp.de> (raw)
Hi,
i currently facing a problem in our testing environment where I see file system corruption with 2.7.1 on iSCSI and Local Storage (LVM).
Trying to bisect, but has anyone observed this before?
Thanks,
Peter
next reply other threads:[~2017-01-13 10:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 10:44 Peter Lieven [this message]
2017-01-17 6:40 ` [Qemu-devel] Data corruption in Qemu 2.7.1 Fam Zheng
2017-01-17 10:14 ` [Qemu-devel] [Qemu-stable] " Peter Lieven
2017-01-17 7:33 ` [Qemu-devel] " Alexandre DERUMIER
2017-01-17 8:03 ` [Qemu-devel] [Qemu-stable] " Fabian Grünbichler
2017-01-17 10:41 ` Paolo Bonzini
2017-01-17 11:22 ` Fabian Grünbichler
2017-01-17 15:03 ` Paolo Bonzini
2017-01-17 16:24 ` Paolo Bonzini
2017-01-18 11:50 ` Fabian Grünbichler
2017-01-18 16:19 ` Fabian Grünbichler
2017-01-18 16:30 ` Paolo Bonzini
2017-01-18 17:17 ` Fabian Grünbichler
2017-01-19 11:59 ` Fabian Grünbichler
2017-01-24 9:35 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5878AF90.8020709@kamp.de \
--to=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).