Add support for verify triggers and verify state saving
This allows you to (for instance) instantly terminate a verify
write workload, and then later that everything was written
correctly up to that very point. This can be useful for testing
powercut scenarios, which is often problematic on storage
devices.
The trigger part is a file based notification scheme, similar
to what is provided for the status dumps. When triggered,
fio will exit immediately and write the verify state safely
to disk. A trigger can be accompanied by a trigger command.
Say you wanted to test powercut safety, the trigger could be
something that immediately cut power to the machine.
The verify state is either saved locally (if run locally),
or saved over the network if run in client/server mode.
Signed-off-by: Jens Axboe <axboe@fb.com>
diff --git a/thread_options.h b/thread_options.h
index 74c3e99..f311e2c 100644
--- a/thread_options.h
+++ b/thread_options.h
@@ -99,6 +99,8 @@
unsigned long long verify_backlog;
unsigned int verify_batch;
unsigned int experimental_verify;
+ unsigned int verify_state;
+ unsigned int verify_state_save;
unsigned int use_thread;
unsigned int unlink;
unsigned int do_disk_util;
@@ -330,6 +332,9 @@
uint64_t verify_backlog;
uint32_t verify_batch;
uint32_t experimental_verify;
+ uint32_t verify_state;
+ uint32_t verify_state_save;
+ uint32_t pad;
uint32_t use_thread;
uint32_t unlink;
uint32_t do_disk_util;
@@ -349,7 +354,6 @@
uint32_t bs_is_seq_rand;
uint32_t random_distribution;
- uint32_t pad;
fio_fp64_t zipf_theta;
fio_fp64_t pareto_h;