Antonio Russo a75af541cf ZTS: limit mmapwrite file size ... commit ee6bf97c77 upstream mmapwrite spawns several threads, all of which perform writes on a file for the purpose of testing the behavior of mmap(2)-ed files. One thread performs an mmap and a write to the beginning of that region, while the others perform regular writes after lseek(2)-ing the end of the file. Because these regular writes are set in a while (1) loop, they will write an unbounded amount of data to disk. The mmap_write_001_pos test script SIGKILLs them after 30 seconds, but on fast testbeds, this may be enough time to exhaust the available space in the filesystem, leading to spurious test failures. Instead, limit the total file size by checking that the lseek return value is no greater than 250 * 1024*1024 bytes, which is less than the default minimum vdev size defined in includes/default.cfg . This also includes part of 2a493a4c71, which checks the return value of lseek. Signed-off-by: Antonio Russo <aerusso@aerusso.net> Closes #14277 Closes #14345		2023-01-09 17:15:22 -08:00
..
callbacks	ZTS: Add a failsafe callback to run after each test	2020-03-10 11:00:56 -07:00
cmd	ZTS: limit mmapwrite file size	2023-01-09 17:15:22 -08:00
include	Add options to zfs redundant_metadata property	2022-11-01 12:25:58 -07:00
tests	skip permission checks for extended attributes	2023-01-05 11:10:28 -08:00
Makefile.am	OpenZFS 7503 - zfs-test should tail ::zfs_dbgmsg on test failure	2017-04-12 13:36:48 -07:00