diff options
author | Kevin Wolf <kwolf@redhat.com> | 2018-06-28 17:05:45 +0200 |
---|---|---|
committer | Kevin Wolf <kwolf@redhat.com> | 2018-06-29 14:20:56 +0200 |
commit | 8b24cd141549b5b264baeddd4e72902cfb5de23b (patch) | |
tree | 2856eb7c876ed7578c0620270344b90b4d0bc6f9 /io | |
parent | 93a3642efcadf4ad6045ccea38a05ff5297dfe26 (diff) |
qcow2: Free allocated clusters on write error
If we managed to allocate the clusters, but then failed to write the
data, there's a good chance that we'll still be able to free the
clusters again in order to avoid cluster leaks (the refcounts are
cached, so even if we can't write them out right now, we may be able to
do so when the VM is resumed after a werror=stop/enospc pause).
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Tested-by: Eric Blake <eblake@redhat.com>
Diffstat (limited to 'io')
0 files changed, 0 insertions, 0 deletions