diff options
| author | Eric Blake <eblake@redhat.com> | 2018-11-13 17:03:19 -0600 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2018-11-19 12:51:40 +0100 |
| commit | 3b94c343f98b660e1c1cf79a8f704151962ecd48 (patch) | |
| tree | 5e5af504bf004891f84ebad4d11ecb498bcfb6ab /tests/qemu-iotests/group | |
| parent | 77d6a21558577fbdd35e65e0e1d03ae07214329f (diff) | |
| download | qemu-3b94c343f98b660e1c1cf79a8f704151962ecd48.zip qemu-3b94c343f98b660e1c1cf79a8f704151962ecd48.tar.gz qemu-3b94c343f98b660e1c1cf79a8f704151962ecd48.tar.bz2 | |
iotests: Add new test 220 for max compressed cluster offset
If you have a capable file system (tmpfs is good, ext4 not so much;
run ./check with TEST_DIR pointing to a good location so as not
to skip the test), it's actually possible to create a qcow2 file
that expands to a sparse 512T image with just over 38M of content.
The test is not the world's fastest (qemu crawling through 256M
bits of refcount table to find the next cluster to allocate takes
several seconds, as does qemu-img check reporting millions of
leaked clusters); but it DOES catch the problem that the previous
patch just fixed where writing a compressed cluster to a full
image ended up overwriting the wrong cluster.
Suggested-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Alberto Garcia <berto@igalia.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'tests/qemu-iotests/group')
| -rw-r--r-- | tests/qemu-iotests/group | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/tests/qemu-iotests/group b/tests/qemu-iotests/group index ebe4fe7..4d19471 100644 --- a/tests/qemu-iotests/group +++ b/tests/qemu-iotests/group @@ -219,6 +219,7 @@ 217 rw auto quick 218 rw auto quick 219 rw auto +220 rw auto 221 rw auto quick 222 rw auto quick 223 rw auto quick |