From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Morrissey Subject: qcow2 corruption? Date: Thu, 8 Jan 2009 14:24:22 -0500 Message-ID: <20090108192422.GA32052@boost.horde.net> References: <20081226210028.GA25127@boost.horde.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: kvm@vger.kernel.org Return-path: Received: from boost.horde.net ([69.55.65.181]:41761 "EHLO boost.horde.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760997AbZAHTYX (ORCPT ); Thu, 8 Jan 2009 14:24:23 -0500 Content-Disposition: inline In-Reply-To: <20081226210028.GA25127@boost.horde.net> Sender: kvm-owner@vger.kernel.org List-ID: 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). john -- John Morrissey _o /\ ---- __o jwm@horde.net _-< \_ / \ ---- < \, www.horde.net/ __(_)/_(_)________/ \_______(_) /_(_)__