diff options
| author | Max Reitz <mreitz@redhat.com> | 2019-05-16 16:43:19 +0200 |
|---|---|---|
| committer | Max Reitz <mreitz@redhat.com> | 2019-06-14 14:16:57 +0200 |
| commit | a3bd71b5773a3664692601e6e181f108e1e4aa41 (patch) | |
| tree | 3d4e4492bad2be83ae01dfb625e03660faf94625 /tests/uefi-test-tools | |
| parent | 9e8dfad045211fbb8f4184285747907517550f23 (diff) | |
| download | qemu-a3bd71b5773a3664692601e6e181f108e1e4aa41.zip qemu-a3bd71b5773a3664692601e6e181f108e1e4aa41.tar.gz qemu-a3bd71b5773a3664692601e6e181f108e1e4aa41.tar.bz2 | |
iotests: Filter 175's allocation information
It is possible for an empty file to take up blocks on a filesystem, for
example:
$ qemu-img create -f raw test.img 1G
Formatting 'test.img', fmt=raw size=1073741824
$ mkfs.ext4 -I 128 -q test.img
$ mkdir test-mount
$ sudo mount -o loop test.img test-mount
$ sudo touch test-mount/test-file
$ stat -c 'blocks=%b' test-mount/test-file
blocks=8
These extra blocks (one cluster) are apparently used for metadata,
because they are always there, on top of blocks used for data:
$ sudo dd if=/dev/zero of=test-mount/test-file bs=1M count=1
1+0 records in
1+0 records out
1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.00135339 s, 775 MB/s
$ stat -c 'blocks=%b' test-mount/test-file
blocks=2056
Make iotest 175 take this into account.
Reported-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Max Reitz <mreitz@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Nir Soffer <nsoffer@redhat.com>
Message-id: 20190516144319.12570-1-mreitz@redhat.com
Signed-off-by: Max Reitz <mreitz@redhat.com>
Diffstat (limited to 'tests/uefi-test-tools')
0 files changed, 0 insertions, 0 deletions