From: J M Cerqueira Esteves <jmce@artenumerica.com>
To: qemu-devel@nongnu.org
Cc: AN support <support@artenumerica.com>
Subject: Re: [Qemu-devel] QCOW image corruption under QEMU 0.9.0
Date: Sun, 25 Feb 2007 02:55:19 +0000 [thread overview]
Message-ID: <45E0FA97.3030103@artenumerica.com> (raw)
In-Reply-To: <45DEE9BA.7040202@artenumerica.com>
J M Cerqueira Esteves wrote:
> After shutting down the guest, I inspected its image files with
> qemu-info, which reported for hda
>
> image: nisaba.hda.qcow
> file format: raw
> virtual size: 4.3G (4596273152 bytes)
> disk size: 4.3G
>
> but hda was supposed to have a virtual size of approximately 20 GB,
> QCOW2 format and a saved snapshot...
And now I got another corrupted image:
This time, after installing some packages in a similar Debian guest,
the system froze while shutting down (using 100% CPU on host).
I then noticed that its supposed QCOW2 image file (a 20 GB virtual disk,
in a by then more than 4GB file) was no longer considered to be a QCOW2
image, as above.
Curiously this damaged image file has 4543348736 bytes.
I wonder if there some new bug triggered by the image file size,
for some size around 4500000000 bytes...
Fortunately this time I have a backup copy of the virtual disk state
just before it was corrupted. I'll try to see what happens if I convert
it from qcow2 to qcow before proceeding. Any suggestions?
Best regards
J Esteves
next prev parent reply other threads:[~2007-02-25 2:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 13:18 [Qemu-devel] QCOW image corruption under QEMU 0.9.0 J M Cerqueira Esteves
2007-02-23 18:42 ` [Qemu-devel] " J M Cerqueira Esteves
2007-02-25 2:02 ` [Qemu-devel] MORE " AN support
2007-02-25 2:55 ` J M Cerqueira Esteves [this message]
2007-02-25 3:38 ` [Qemu-devel] " J M Cerqueira Esteves
2007-02-25 6:01 ` J M Cerqueira Esteves
2007-02-25 8:07 ` [Qemu-devel] QEMU with smp Danny Chieh-Yao, Cheng
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=45E0FA97.3030103@artenumerica.com \
--to=jmce@artenumerica.com \
--cc=qemu-devel@nongnu.org \
--cc=support@artenumerica.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.