From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: qcow2 corruption?
Date: Thu, 08 Jan 2009 14:33:28 -0600
Message-ID: <49666318.3050706@codemonkey.ws>
References: <20081226210028.GA25127@boost.horde.net> <20090108192422.GA32052@boost.horde.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org
To: John Morrissey <jwm@horde.net>
Return-path: <kvm-owner@vger.kernel.org>
Received: from qw-out-2122.google.com ([74.125.92.24]:43478 "EHLO
	qw-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1754600AbZAHUdh (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 8 Jan 2009 15:33:37 -0500
Received: by qw-out-2122.google.com with SMTP id 3so8085072qwe.37
        for <kvm@vger.kernel.org>; Thu, 08 Jan 2009 12:33:36 -0800 (PST)
In-Reply-To: <20090108192422.GA32052@boost.horde.net>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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.
>
> In a few cases, I've managed to finish an installation, but the resulting
> filesystem is strangely corrupt:
>
> # file /usr/bin/w.procps
> /usr/bin/w.procps: gzip compressed data, was "aptitude.8", from Unix, last modified: Wed Mar 14 14:11:18 2007, max compression
>
> I've tried with the Debian packaging of KVM 79 and 82; both exhibit the same
> behavior (disclaimer: Debian has about a dozen patches in their kvm
> packaging, but they all seem to be changes to the build/install process or
> security-related). Host running KVM is up-to-date Debian lenny
> (64-bit/amd64) running kernel 2.6.26 (Debian linux-image-2.6.26-1-amd64
> 2.6.26-12).
>   

There are patches that touch the block layer.  Please try to reproduce 
on vanilla kvm.  I don't trust the debian patches.

Regards,

Anthony Liguori

> john
>