diff options
| author | Eric Blake <eblake@redhat.com> | 2025-05-23 11:27:22 -0500 |
|---|---|---|
| committer | Eric Blake <eblake@redhat.com> | 2025-05-29 16:37:20 -0500 |
| commit | ed1c336119c084159575ae9d4fd9171bd500f7e4 (patch) | |
| tree | 33caebc91c97f3bc4075fdf7a4d222fafb5b348e /python/scripts | |
| parent | d2b3e32bf7395c710ba44585520d837f6330fa70 (diff) | |
| download | qemu-ed1c336119c084159575ae9d4fd9171bd500f7e4.zip qemu-ed1c336119c084159575ae9d4fd9171bd500f7e4.tar.gz qemu-ed1c336119c084159575ae9d4fd9171bd500f7e4.tar.bz2 | |
iotests: Improve mirror-sparse on ext4 and xfs
Fiona reported that an ext4 filesystem on top of LVM can sometimes
report over-allocation to du (based on the heuristics the filesystem
is making while observing the contents being mirrored); even though
the contents and actual size matched, about 50% of the time the size
reported by disk_usage was too large by 4k, failing the test. In
auditing other iotests, this is a common problem we've had to deal
with.
Meanwhile, Markus reported that an xfs filesystem reports disk usage
at a default granularity of 1M (so the sparse file occupies 3M, since
it has just over 2M data).
Reported-by: Fiona Ebner <f.ebner@proxmox.com>
Reported-by: Markus Armbruster <armbru@redhat.com>
Fixes: c0ddcb2c ("tests: Add iotest mirror-sparse for recent patches")
Signed-off-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Fiona Ebner <f.ebner@proxmox.com>
Tested-by: Fiona Ebner <f.ebner@proxmox.com>
Message-ID: <20250523163041.2548675-7-eblake@redhat.com>
[eblake: Also fix xfs issue]
Signed-off-by: Eric Blake <eblake@redhat.com>
Diffstat (limited to 'python/scripts')
0 files changed, 0 insertions, 0 deletions