Re: [Qemu-devel] Failing QEMU iotest 175

[Max Reitz <mreitz@redhat.com>]

[-- Attachment #1: Type: text/plain, Size: 2211 bytes --]

On 28.04.19 17:18, Thomas Huth wrote:
> QEMU iotest 175 is failing for me when I run it with -raw:
> 
> $ ./check -raw 175
> QEMU          --
> "/home/thuth/tmp/qemu-build/tests/qemu-iotests/../../x86_64-softmmu/qemu-system-x86_64"
> -nodefaults -machine accel=qtest
> QEMU_IMG      --
> "/home/thuth/tmp/qemu-build/tests/qemu-iotests/../../qemu-img"
> QEMU_IO       --
> "/home/thuth/tmp/qemu-build/tests/qemu-iotests/../../qemu-io"  --cache
> writeback -f raw
> QEMU_NBD      --
> "/home/thuth/tmp/qemu-build/tests/qemu-iotests/../../qemu-nbd"
> IMGFMT        -- raw
> IMGPROTO      -- file
> PLATFORM      -- Linux/x86_64 thuth 3.10.0-957.10.1.el7.x86_64
> TEST_DIR      -- /home/thuth/tmp/qemu-build/tests/qemu-iotests/scratch
> SOCKET_SCM_HELPER --
> /home/thuth/tmp/qemu-build/tests/qemu-iotests/socket_scm_helper
> 
> 175         - output mismatch (see 175.out.bad)
> --- /home/thuth/devel/qemu/tests/qemu-iotests/175.out	2019-04-23
> 16:43:12.000000000 +0200
> +++ /home/thuth/tmp/qemu-build/tests/qemu-iotests/175.out.bad	2019-04-28
> 17:17:32.000000000 +0200
> @@ -2,17 +2,17 @@
> 
>  == creating image with default preallocation ==
>  Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=1048576
> -size=1048576, blocks=0
> +size=1048576, blocks=2
> 
>  == creating image with preallocation off ==
>  Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=1048576 preallocation=off
> -size=1048576, blocks=0
> +size=1048576, blocks=2
> 
>  == creating image with preallocation full ==
>  Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=1048576 preallocation=full
> -size=1048576, blocks=2048
> +size=1048576, blocks=2050
> 
>  == creating image with preallocation falloc ==
>  Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=1048576
> preallocation=falloc
> -size=1048576, blocks=2048
> +size=1048576, blocks=2050
>   *** done
> Failures: 175
> Failed 1 of 1 tests
> 
> Any ideas how to fix this?

Hm.  What output does

$ touch foo
$ stat -c "size=%s, blocks=%b" foo
$ truncate -s 1M foo
$ stat -c "size=%s, blocks=%b" foo

give for you?

If any of that returns blocks=2, we can probably just use that operation
to fix the result, then.

Max


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]