From: "Vaughan" <cxt9401@163.com>
To: fio@vger.kernel.org
Cc: cxt9401@163.com
Subject: How to ensure split verification will generate the same configs as write phase?
Date: Tue, 27 Feb 2018 18:45:46 +0800 [thread overview]
Message-ID: <000801d3afb8$1ffb6a10$5ff23e30$@163.com> (raw)
Hi all,
I want fio to do an split verification for RAID as did in
https://github.com/axboe/fio/issues/468. Once written, the verification will
be repeat several times for raid recovery for each disk.
The example job file is as below:
----- write job -----
[global]
do_verify=0
iodepth=32
filename=/dev/nvme0n6
rw=randwrite
ioengine=libaio
verify=crc32c-intel
direct=1
verify_offset=100
bs=4096
[job_0]
size=209715200
offset=0
----- read job -----
[global]
do_verify=1
verify_state_load=1
iodepth=32
filename=/dev/nvme0n6
rw=read
ioengine=libaio
verify=crc32c-intel
direct=1
verify_offset=100
bs=4096
[job_0]
size=209715200
offset=0
I don't see it use the same randseed. Can it generate the same offset as
write phase without randseed= option set?
If I use randbs= to also use an random write blocksizes, how can I ensure
the verification will do the same as write?
Can write_iolog ensure that? However, I suppose it may slow down the write
speed and randomness of test.
Regards,
Vaughan
next reply other threads:[~2018-02-27 10:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 10:45 Vaughan [this message]
2018-02-27 11:59 ` How to ensure split verification will generate the same configs as write phase? Sitsofe Wheeler
2018-02-28 8:44 ` 答复: " Vaughan
2018-02-28 16:15 ` Sitsofe Wheeler
2018-03-09 6:11 ` 答复: " Vaughan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000801d3afb8$1ffb6a10$5ff23e30$@163.com' \
--to=cxt9401@163.com \
--cc=fio@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox