From: Jens Axboe <axboe@kernel.dk>
To: Gary Foster <gpfwestie@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: verify with norandommap
Date: Sun, 02 Sep 2012 21:39:39 -0600 [thread overview]
Message-ID: <5044267B.8060408@kernel.dk> (raw)
In-Reply-To: <CAAyzu8gnC9ukuSV5UUxPcp-x9Q-6sf5OV2nPpOVnchMZ5LqKDw@mail.gmail.com>
On 2012-09-02 18:14, Gary Foster wrote:
> I realise most people are using Fio to do performance testing, ie
> replicating Windows IOMeter.
>
> But surely there are some guys using Fio for data integrity testing,
> could you guys give me some help with this ?
It will work OK with norandommap for your workload. If you have mixed
block sizes, then you could run into verification failures if smaller
blocks overwrite parts of a bigger verification piece. With pattern
verification and a pattern size set to the smallest blocksize that
should work too, though.
If you see the 'V', it's definitely verifying. The comment on
norandommap refers to seeing spurious verification failures, not that it
wont verify at all. Your job file should be fine.
--
Jens Axboe
prev parent reply other threads:[~2012-09-03 3:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 14:16 verify with norandommap Gary Foster
2012-09-03 0:14 ` Gary Foster
2012-09-03 3:39 ` Jens Axboe [this message]
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=5044267B.8060408@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=gpfwestie@gmail.com \
/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