mirror_zfs/tests/runfiles
Rob Norris 1f8c39ddb2 ZTS: test response of various sync methods under different failmodes
These are all the same shape: set up the pool to suspend on first write,
then perform some write+sync operation. The pool should suspend, and the
sync operation should respond according to the failmode= property.

We test fsync(), msync() and two forms of write() (open with O_SYNC, and
async with sync=always), which all take slightly different paths to
zil_commit() and back.

A helper function is included to do the write+sync sequence with mmap()
and msync(), since I didn't find a convenient tool to do that.

Sponsored-by: Klara, Inc.
Sponsored-by: Wasabi Technology, Inc.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Alexander Motin <alexander.motin@TrueNAS.com>
Signed-off-by: Rob Norris <rob.norris@klarasystems.com>
Closes #17398
2025-08-08 16:42:35 -07:00
..
bclone.run SPDX: license tags: CDDL-1.0 2025-03-13 17:56:27 -07:00
common.run ZTS: test response of various sync methods under different failmodes 2025-08-08 16:42:35 -07:00
freebsd.run SPDX: license tags: CDDL-1.0 2025-03-13 17:56:27 -07:00
linux.run Fix TestGroup warning due to missing tags 2025-06-19 14:41:31 -07:00
longevity.run SPDX: license tags: CDDL-1.0 2025-03-13 17:56:27 -07:00
perf-regression.run SPDX: license tags: CDDL-1.0 2025-03-13 17:56:27 -07:00
sanity.run Implement physical rewrites 2025-08-06 10:36:56 -07:00
sunos.run SPDX: license tags: CDDL-1.0 2025-03-13 17:56:27 -07:00