From: Ben Taylor <sol10x86@cox.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QCOW(2) image corruption under QEMU 0.9.0 reproducible
Date: Fri, 16 Mar 2007 13:00:26 -0400 [thread overview]
Message-ID: <29748678.1174064426173.JavaMail.root@eastrmwml07.cox.net> (raw)
---- J M Cerqueira Esteves <jmce@artenumerica.com> wrote:
> herbie hancock wrote:
> > Hello, i had also a reproducible disk crash:
> > info of the last good image, size is about 3,5GB
> >
> > I never experienced such a bad problem with qemu before, maybe it is a problem with qcow2 format ?
>
> After the problems with qcow2 images which I reported here a few weeks
> ago, I've only been using qcow images (under QEMU 0.9.0), without such
> surprises. So it seems qemu has some bug related to qcow2 images,
> maybe manifesting itself only after they get larger than 4GB...
I suspect I saw problems with qcow2 images as well. I was able to suspend
a Solaris Nevada B58 install and use savevm about 30% into the install and
restart it later. As the image completd, the file system went all to hell
with corruption that was impossible to fix. At the time, I attributed it to
the Solaris install (thinking it might have something to do with the
cmpxchg8b bug that was later fixed), but I suspect with the multiple
reports I've seen, I'm now thinking I saw the same thing.
I'm testing conversion of a qcow image to a qcow2 image. We'll see how
that goes
Ben
next reply other threads:[~2007-03-16 17:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 17:00 Ben Taylor [this message]
2007-03-16 18:17 ` [Qemu-devel] QCOW(2) image corruption under QEMU 0.9.0 reproducible Julian Seward
-- strict thread matches above, loose matches on Subject: below --
2007-03-17 16:48 herbie hancock
2007-03-14 23:20 herbie hancock
2007-03-15 9:59 ` Julian Seward
2007-03-15 14:00 ` Thiemo Seufer
2007-03-16 12:01 ` J M Cerqueira Esteves
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=29748678.1174064426173.JavaMail.root@eastrmwml07.cox.net \
--to=sol10x86@cox.net \
--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;
as well as URLs for NNTP newsgroup(s).