From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HSH3G-0007NH-ME for qemu-devel@nongnu.org; Fri, 16 Mar 2007 14:21:18 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HSH3G-0007N0-Ak for qemu-devel@nongnu.org; Fri, 16 Mar 2007 14:21:18 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HSH3G-0007Mx-1o for qemu-devel@nongnu.org; Fri, 16 Mar 2007 13:21:18 -0500 Received: from mtaout02-winn.ispmail.ntl.com ([81.103.221.48]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HSH26-0005m1-T9 for qemu-devel@nongnu.org; Fri, 16 Mar 2007 14:20:07 -0400 From: Julian Seward Subject: Re: [Qemu-devel] QCOW(2) image corruption under QEMU 0.9.0 reproducible Date: Fri, 16 Mar 2007 18:17:28 +0000 References: <29748678.1174064426173.JavaMail.root@eastrmwml07.cox.net> In-Reply-To: <29748678.1174064426173.JavaMail.root@eastrmwml07.cox.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200703161817.28876.jseward@acm.org> 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, sol10x86@cox.net I ran QEMU on Valgrind for several hours last night, including a couple of boot-shutdown cycles of RedHat8, and lots of file copying/deletion in the guest to get the qcow2 image up to 8GB and generally cause a lot of disk IO. I got no memory errors whatsoever from Valgrind and got no filesystem corruption, so I guess I didn't trigger the bug. Really the first thing to do is establish a reliable way to reproduce it. J On Friday 16 March 2007 17:00, Ben Taylor wrote: > ---- 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 > > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel