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(-)