summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKevin Wolf <kwolf@redhat.com>2010-04-21 11:37:52 +0200
committerKevin Wolf <kwolf@redhat.com>2010-07-14 11:45:07 +0200
commit729862401ddbf2554807f085e234e26625ba542c (patch)
treeededfaa69c7856d66d150604322e84dad84c0356
parentvmdk: Fix COW (diff)
downloadqemu-kvm-729862401ddbf2554807f085e234e26625ba542c.tar.gz
qemu-kvm-729862401ddbf2554807f085e234e26625ba542c.tar.bz2
qemu-kvm-729862401ddbf2554807f085e234e26625ba542c.zip
qcow2: Remove abort on free_clusters failure
While it's true that during regular operation free_clusters failure would be a bug, an I/O error can always happen. There's no need to kill the VM, the worst thing that can happen (and it will) is that we leak some clusters. Signed-off-by: Kevin Wolf <kwolf@redhat.com> (cherry picked from commit 003fad6e2cae5311d3aea996388c90e3ab17de90)
-rw-r--r--block/qcow2-refcount.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/block/qcow2-refcount.c b/block/qcow2-refcount.c
index 465d5d36e..ff2cf6db2 100644
--- a/block/qcow2-refcount.c
+++ b/block/qcow2-refcount.c
@@ -631,7 +631,7 @@ void qcow2_free_clusters(BlockDriverState *bs,
ret = update_refcount(bs, offset, size, -1);
if (ret < 0) {
fprintf(stderr, "qcow2_free_clusters failed: %s\n", strerror(-ret));
- abort();
+ /* TODO Remember the clusters to free them later and avoid leaking */
}
}