tree 4a61d99904abee144ab81edbfad65e72305746b6
parent 2581b5195ad1dc4a7d5184b4a641c570faafb813
author Jens Axboe <axboe@fb.com> 1415676840 -0700
committer Mohamad Ayyash <mkayyash@google.com> 1425693483 -0800

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>