When verify workloads with the verify_state_load option target an offset
that is not saved in the verify state file, verify_state_should_stop()
function returns false and it stops the verify workloads. This workloads
stop is made without providing a message to users, making it difficult
for them to understand why they stopped. Print a message to inform users
why the verify workloads stopped.
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@xxxxxxx>
---
verify.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/verify.c b/verify.c
index 2e113862..63b63718 100644
--- a/verify.c
+++ b/verify.c
@@ -1892,5 +1892,7 @@ int verify_state_should_stop(struct thread_data *td, struct io_u *io_u)
/*
* Not found, we have to stop
*/
+ log_info("Stop verify because offset %llu in %s is not recorded in verify state\n",
+ io_u->verify_offset, f->file_name);
return 1;
}
--
2.47.0
