From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HL8ib-0005WW-0g
	for qemu-devel@nongnu.org; Sat, 24 Feb 2007 21:02:29 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HL8iY-0005UB-Cs
	for qemu-devel@nongnu.org; Sat, 24 Feb 2007 21:02:27 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HL8iY-0005Tn-4i
	for qemu-devel@nongnu.org; Sat, 24 Feb 2007 21:02:26 -0500
Received: from merlin.artenumerica.net ([80.68.90.14])
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1HL8iX-0004hi-Gb
	for qemu-devel@nongnu.org; Sat, 24 Feb 2007 21:02:25 -0500
Message-ID: <45E0EE25.9040706@artenumerica.com>
From: AN support <support@artenumerica.com>
MIME-Version: 1.0
References: <45DEE9BA.7040202@artenumerica.com>
In-Reply-To: <45DEE9BA.7040202@artenumerica.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] MORE QCOW image corruption under QEMU 0.9.0
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
Date: Sun, 25 Feb 2007 02:02:29 -0000
To: qemu-devel@nongnu.org
Cc: AN support <support@artenumerica.com>, J Sebrosa <sebrosa@gmail.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 more suggestions?

Best regards
                               J Esteves