Mark do_verify and verify_fatal as booleans
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
diff --git a/HOWTO b/HOWTO
index ffd8d0a..3bee1a2 100644
--- a/HOWTO
+++ b/HOWTO
@@ -569,7 +569,7 @@
to repeat the same workload a given number of times. Defaults
to 1.
-do_verify=int Run the verify phase after a write phase. Only makes sense if
+do_verify=bool Run the verify phase after a write phase. Only makes sense if
verify is set. Defaults to 1.
verify=str If writing to a file, fio can verify the file contents
@@ -632,7 +632,7 @@
buffer at the time. The verify_pattern cannot be larger than
a 32-bit quantity.
-verify_fatal=int Normally fio will keep checking the entire contents
+verify_fatal=bool Normally fio will keep checking the entire contents
before quitting on a block verification failure. If this
option is set, fio will exit the job on the first observed
failure.
diff --git a/options.c b/options.c
index 62bbb43..f1ee6bc 100644
--- a/options.c
+++ b/options.c
@@ -651,7 +651,7 @@
},
{
.name = "do_verify",
- .type = FIO_OPT_INT,
+ .type = FIO_OPT_BOOL,
.off1 = td_var_offset(do_verify),
.help = "Run verification stage after write",
.def = "1",
@@ -690,7 +690,7 @@
},
{
.name = "verify_fatal",
- .type = FIO_OPT_INT,
+ .type = FIO_OPT_BOOL,
.off1 = td_var_offset(verify_fatal),
.def = "0",
.help = "Exit on a single verify failure, don't continue",