From: Chris Wright <chrisw@sous-sol.org>
To: Kevin Wolf <kwolf@suse.de>
Cc: Jamie Lokier <jamie@shareable.org>,
qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>,
Laurent Vivier <laurent@lvivier.info>
Subject: Re: [Qemu-devel] qcow2 corruption observed, fixed by reverting old change
Date: Wed, 11 Feb 2009 21:45:30 -0800 [thread overview]
Message-ID: <20090212054530.GT27684@sequoia.sous-sol.org> (raw)
In-Reply-To: <4992C77D.4030104@suse.de>
* Kevin Wolf (kwolf@suse.de) wrote:
> I would suspect that simply having a 64 bit host isn't enough to trigger
> the problem. These patches were in for half a year now without anyone
> noticing such failure.
BTW, we've seen similar corruption, but not narrowed it down successfully as
it's been quite difficult to trigger.
thanks,
-chris
next prev parent reply other threads:[~2009-02-12 5:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 7:00 qcow2 corruption observed, fixed by reverting old change Jamie Lokier
2009-02-11 9:57 ` [Qemu-devel] " Kevin Wolf
2009-02-11 11:27 ` Jamie Lokier
2009-02-11 11:41 ` Jamie Lokier
2009-02-11 12:41 ` Kevin Wolf
2009-02-11 16:48 ` Jamie Lokier
2009-02-12 22:57 ` Consul
2009-02-12 23:19 ` Consul
2009-02-16 12:44 ` [Qemu-devel] " Kevin Wolf
2009-02-17 0:43 ` Jamie Lokier
2009-03-06 22:37 ` Filip Navara
2009-02-12 5:45 ` Chris Wright [this message]
2009-02-12 11:08 ` Johannes Schindelin
2009-02-13 6:41 ` Marc Bevand
2009-02-13 11:16 ` Kevin Wolf
2009-02-13 16:23 ` [Qemu-devel] " Jamie Lokier
2009-02-13 18:43 ` Chris Wright
2009-02-14 6:31 ` Marc Bevand
2009-02-14 22:28 ` Dor Laor
2009-02-15 2:27 ` Jamie Lokier
2009-02-15 7:56 ` Marc Bevand
2009-02-15 2:37 ` Jamie Lokier
2009-02-15 10:57 ` Gleb Natapov
2009-02-15 11:46 ` Marc Bevand
2009-02-15 11:54 ` Marc Bevand
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=20090212054530.GT27684@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=jamie@shareable.org \
--cc=kvm@vger.kernel.org \
--cc=kwolf@suse.de \
--cc=laurent@lvivier.info \
--cc=qemu-devel@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