public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: John Morrissey <jwm@horde.net>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kvm@vger.kernel.org
Subject: Re: qcow2 corruption?
Date: Thu, 8 Jan 2009 22:42:18 -0500	[thread overview]
Message-ID: <20090109034218.GA5921@boost.horde.net> (raw)
In-Reply-To: <49666318.3050706@codemonkey.ws>

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?

Sorry for the bother, guys.

john
-- 
John Morrissey          _o            /\         ----  __o
jwm@horde.net        _-< \_          /  \       ----  <  \,
www.horde.net/    __(_)/_(_)________/    \_______(_) /_(_)__

  reply	other threads:[~2009-01-09  3:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-26 21:00 BUG() with SCSI-interfaced disk images John Morrissey
2009-01-07 20:19 ` John Morrissey
2009-01-07 22:34   ` Ryan Harper
2009-01-08  2:13     ` John Morrissey
2009-01-08 14:01       ` Ryan Harper
2009-01-08 18:15         ` John Morrissey
2009-01-08 19:24 ` qcow2 corruption? John Morrissey
2009-01-08 20:10   ` Ryan Harper
2009-01-08 20:16     ` John Morrissey
2009-01-08 20:33   ` Anthony Liguori
2009-01-09  3:42     ` John Morrissey [this message]
2009-01-09 13:34       ` Ryan Harper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090109034218.GA5921@boost.horde.net \
    --to=jwm@horde.net \
    --cc=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox