From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=56755 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OUjpY-0005XJ-J0 for qemu-devel@nongnu.org; Fri, 02 Jul 2010 13:15:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OUjpW-0007lm-S9 for qemu-devel@nongnu.org; Fri, 02 Jul 2010 13:15:12 -0400 Received: from mx1.redhat.com ([209.132.183.28]:51375) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OUjpW-0007lZ-KV for qemu-devel@nongnu.org; Fri, 02 Jul 2010 13:15:10 -0400 Received: from int-mx04.intmail.prod.int.phx2.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.17]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o62HF96n028231 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 2 Jul 2010 13:15:10 -0400 From: Kevin Wolf Date: Fri, 2 Jul 2010 19:14:58 +0200 Message-Id: <1278090900-12832-1-git-send-email-kwolf@redhat.com> Subject: [Qemu-devel] [PATCH 0/2] Improve qemu-img check output List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: kwolf@redhat.com 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(-)