From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HSFoZ-0005xt-JP for qemu-devel@nongnu.org; Fri, 16 Mar 2007 13:02:03 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HSFoV-0005x9-So for qemu-devel@nongnu.org; Fri, 16 Mar 2007 13:02:03 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HSFoU-0005x0-TH for qemu-devel@nongnu.org; Fri, 16 Mar 2007 12:01:59 -0500 Received: from eastrmmtao105.cox.net ([68.230.240.47]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HSFnF-0003oV-O1 for qemu-devel@nongnu.org; Fri, 16 Mar 2007 13:00:42 -0400 Message-ID: <29748678.1174064426173.JavaMail.root@eastrmwml07.cox.net> Date: Fri, 16 Mar 2007 13:00:26 -0400 From: Ben Taylor Subject: Re: [Qemu-devel] QCOW(2) image corruption under QEMU 0.9.0 reproducible MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Reply-To: sol10x86@cox.net, 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 ---- J M Cerqueira Esteves 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