From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HSB8z-00028O-6v for qemu-devel@nongnu.org; Fri, 16 Mar 2007 08:02:49 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HSB8y-00028C-Li for qemu-devel@nongnu.org; Fri, 16 Mar 2007 08:02:48 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HSB8y-000289-F5 for qemu-devel@nongnu.org; Fri, 16 Mar 2007 07:02:48 -0500 Received: from merlin.artenumerica.net ([80.68.90.14]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HSB7r-0004SW-5x for qemu-devel@nongnu.org; Fri, 16 Mar 2007 08:01:39 -0400 Received: from [10.10.1.21] (213-205-71-182.net.novis.pt [213.205.71.182]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by merlin.artenumerica.net (Postfix) with ESMTP id 7A79C50283 for ; Fri, 16 Mar 2007 12:01:26 +0000 (GMT) Message-ID: <45FA8711.60404@artenumerica.com> Date: Fri, 16 Mar 2007 12:01:21 +0000 From: J M Cerqueira Esteves MIME-Version: 1.0 Subject: Re: [Qemu-devel] QCOW(2) image corruption under QEMU 0.9.0 reproducible References: <1730805162@web.de> In-Reply-To: <1730805162@web.de> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 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... Best regards J Esteves