From: Darrick J. Wong Date: Mon, 10 Nov 2025 18:27:35 +0000 (-0800) Subject: generic/774: reduce file size X-Git-Tag: v2025.11.18~7 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=c5e62a6b850375f8970cd5fb8a48b43fc0950a3e;p=xfstests-dev.git generic/774: reduce file size We've gotten complaints about this test taking hours to run and producing stall warning on test VMs with a large number of cpu cores. I think this is due to the maximum atomic write unit being very large on XFS where we can fall back to a software-based out of place write implementation. On the victim machine, the atomic write max is 4MB and there are 24 CPUs. As a result, aw_bsize to be 1MB, so the file size is 1MB * 24 * 2 * 100 == 4.8GB. I set up a test machine with fast storage and 24 CPUs, and the atomic writes poked along at 25MB/s and the total runtime was 300s. On spinning rust those stats will be much worse. Let's try backing the file size off by 10x and see if that eases the complaints. Cc: fstests@vger.kernel.org # v2025.10.20 Fixes: 9117fb93b41c38 ("generic: Add atomic write test using fio verify on file mixed mappings") Signed-off-by: Darrick J. Wong Reviewed-by: Ojaswin Mujoo Reviewed-by: Christoph Hellwig Signed-off-by: Zorro Lang --- diff --git a/tests/generic/774 b/tests/generic/774 index 7a4d7016..28886ed5 100755 --- a/tests/generic/774 +++ b/tests/generic/774 @@ -29,7 +29,7 @@ aw_bsize=$(_max "$awu_min_write" "$((awu_max_write/4))") fsbsize=$(_get_block_size $SCRATCH_MNT) threads=$(_min "$(($(nproc) * 2 * LOAD_FACTOR))" "100") -filesize=$((aw_bsize * threads * 100)) +filesize=$((aw_bsize * threads * 10)) depth=$threads aw_io_size=$((filesize / threads)) aw_io_inc=$aw_io_size