From: John Morrissey <jwm@horde.net>
To: kvm@vger.kernel.org
Subject: qcow2 corruption?
Date: Thu, 8 Jan 2009 14:24:22 -0500 [thread overview]
Message-ID: <20090108192422.GA32052@boost.horde.net> (raw)
In-Reply-To: <20081226210028.GA25127@boost.horde.net>
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/ __(_)/_(_)________/ \_______(_) /_(_)__
next prev parent reply other threads:[~2009-01-08 19:24 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 ` John Morrissey [this message]
2009-01-08 20:10 ` qcow2 corruption? Ryan Harper
2009-01-08 20:16 ` John Morrissey
2009-01-08 20:33 ` Anthony Liguori
2009-01-09 3:42 ` John Morrissey
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=20090108192422.GA32052@boost.horde.net \
--to=jwm@horde.net \
--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