But what about in the case of a verify job where we want verification
done (do_verify)? Should we exclude the runtime & time_based settings
from the validation/verification job?
http://www.coderplay.org/filesysdev/FIO-Data-Integrity-Test.html
"However, if the job file specifies to run based on time rather than
total number of bytes (setting runtime=int and time_based), then
do_verify() is not performed. "
On 2016-07-26 06:15:34 +0000, Sitsofe Wheeler said:
On 26 July 2016 at 00:15, Saeed
<ionictea@xxxxxxxxx> wrote:
Here's the example:
[global]
bs=4k
ioengine=libaio
iodepth=32
size=1g
direct=1
time_based=1
runtime=300
filename=/dev/sdb
group_reporting
numjobs=1
# validation
do_verify=1
verify_fatal=1
verify_dump=1
verify_pattern=0x00000001
[sequential]
rw=readwrite
stonewall
[random]
rw=randrw
stonewall
So with this job file there are two job declarations (sequential & random).
Does the time_based & runtime requirement apply to the entire job as a whole
or per job declaration?
time_based and runtime are per job (like nearly all fio options) so
this job file above will take 600 seconds to complete. This is easy to
check with a smaller and simpler job file:
[global]
runtime=5
time_based
size=10M
stonewall
filename=/tmp/fiotmp
[job1]
[job2]
The stonewall forces the jobs to run one after the other and the
results will show long each job ran for. If necessary we can easily
use a program like time to see how long the total running time turned
out to be.
Remember that runtime applies to all parts of a job. If a job is
supposed to verify after it has finished writing but the runtime is
exceeded during the writing part then no verification will occur.
--
To unsubscribe from this list: send the line "unsubscribe fio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
