From: Kevin Wolf <kwolf@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] Improve qemu-img check output
Date: Fri, 2 Jul 2010 19:14:58 +0200 [thread overview]
Message-ID: <1278090900-12832-1-git-send-email-kwolf@redhat.com> (raw)
qemu-img check produces messages that are hard to understand. Even worse is
that in the end it just says something like "42 errors" with no further
explanation. Recently I got bug reports from people who though that their image
was corrupted, when in fact there were only a few leaked clusters after a
crash.
This series tries to tell the user if it's real corruption, leaked clusters or
something that went wrong during the check.
Kevin Wolf (2):
qemu-img check: Distinguish different kinds of errors
qcow2/vdi: Change check to distinguish error cases
block.c | 9 ++-
block.h | 10 ++++-
block/qcow2-refcount.c | 120 ++++++++++++++++++++++++++----------------------
block/qcow2.c | 4 +-
block/qcow2.h | 2 +-
block/vdi.c | 10 ++--
block_int.h | 7 ++-
qemu-img.c | 62 +++++++++++++++++++------
8 files changed, 140 insertions(+), 84 deletions(-)
next reply other threads:[~2010-07-02 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 17:14 Kevin Wolf [this message]
2010-07-02 17:14 ` [Qemu-devel] [PATCH 1/2] qemu-img check: Distinguish different kinds of errors Kevin Wolf
2010-07-06 10:51 ` MORITA Kazutaka
2010-07-06 11:01 ` Kevin Wolf
2010-07-06 11:03 ` [Qemu-devel] [PATCH v2 " Kevin Wolf
2010-07-02 17:15 ` [Qemu-devel] [PATCH 2/2] qcow2/vdi: Change check to distinguish error cases Kevin Wolf
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=1278090900-12832-1-git-send-email-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).