Rob N 4725e543be zinject: "no-op" error injection ... When injected, this causes the matching IO to appear to succeed, but the actual work is never submitted to the physical device. This can be used to simulate a write-back cache servicing a write, but the backing device has failed and the cache cannot complete the operation in the background. Sponsored-by: Klara, Inc. Sponsored-by: Wasabi Technology, Inc. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Rob Norris <rob.norris@klarasystems.com> Closes #16085		2024-04-15 13:52:20 -07:00
..
callbacks	Split functional testings via github action matrix	2023-03-15 10:41:05 -07:00
cmd	fix: variable type with zfs-tests/cmd/clonefile.c	2024-01-17 09:06:14 -08:00
include	ZTS: Skip cross-fs bclone tests if FreeBSD < 14.0	2024-02-16 08:59:56 -08:00
tests	zinject: "no-op" error injection	2024-04-15 13:52:20 -07:00
.gitignore	autoconf: use include directives instead of recursing down cmd	2022-05-10 10:18:38 -07:00
Makefile.am	tests: add test for vdev_disk page alignment check	2024-04-11 14:42:46 -07:00