From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ryan Harper Subject: Re: qcow2 corruption? Date: Fri, 9 Jan 2009 07:34:46 -0600 Message-ID: <20090109133446.GJ13481@us.ibm.com> References: <20081226210028.GA25127@boost.horde.net> <20090108192422.GA32052@boost.horde.net> <49666318.3050706@codemonkey.ws> <20090109034218.GA5921@boost.horde.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Anthony Liguori , kvm@vger.kernel.org To: John Morrissey Return-path: Received: from e38.co.us.ibm.com ([32.97.110.159]:43027 "EHLO e38.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752669AbZAINex (ORCPT ); Fri, 9 Jan 2009 08:34:53 -0500 Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e38.co.us.ibm.com (8.13.1/8.13.1) with ESMTP id n09DXPou003627 for ; Fri, 9 Jan 2009 06:33:25 -0700 Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id n09DYoCR180580 for ; Fri, 9 Jan 2009 06:34:50 -0700 Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n09DYo9x017135 for ; Fri, 9 Jan 2009 06:34:50 -0700 Content-Disposition: inline In-Reply-To: <20090109034218.GA5921@boost.horde.net> Sender: kvm-owner@vger.kernel.org List-ID: * John Morrissey [2009-01-08 21:44]: > On Thu, Jan 08, 2009 at 02:33:28PM -0600, Anthony Liguori wrote: > > John Morrissey wrote: > > >I'm encountering what seems like disk corruption when using qcow2 images, > > >created with 'kvm-img create -f qcow2 image.qcow2 15G'. > > > > > >A simple test case is to use the Debian installer (I'm using the lenny > > >rc1 images from http://www.debian.org/devel/debian-installer/) to install > > >a new domain. The qcow2 file on disk grows due to the mkfs(8) activity, > > >then the installer faults while trying to mount the root filesystem > > >(Invalid argument). 'fdisk -l' shows that the partition table just > > >created by the installer is gone. > > > > There are patches that touch the block layer. Please try to reproduce > > on vanilla kvm. I don't trust the debian patches. > > Couldn't reproduce this with Debian packaging minus its patch for > CVE-2008-0928 (taken from Fedora FWIW), which is the only one touching the > block layer. > > Upon further scrutiny, I realized I pooched updating the patch for KVM 82. > The value for the BDRV_O_AUTOGROW constant introduced in that patch collides > with a new BDRV_ constant introduced between KVM 79 and 82. Changing the > constant's value (Fedora project has an updated patch, too) fixes this. > > Ryan, this seems to fix the SCSI BUGging, too. I figure you won't want to > pursue that further? excellent! I had seen the error before but only while developing some new code for the scsi device, so it was a little surprising to see. If you can't recreate now, I think we're done. =) > > Sorry for the bother, guys. np, thanks for testing. -- Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx ryanh@us.ibm.com