Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Suresh Dhanarajan <sureshdrajan@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: query on verify_dump option
Date: Thu, 05 Apr 2012 18:16:50 -0600	[thread overview]
Message-ID: <4F7E35F2.5010701@kernel.dk> (raw)
In-Reply-To: <CAN8qX8YZoZ2TtcqU0QOTEguHoqsYQRuMoFvRsT3JTJc9Uba19w@mail.gmail.com>

On 2012-04-05 17:20, Suresh Dhanarajan wrote:
> Hi,
> 
> I am trying data integration cases with verify_pattern option.
> I am not seeing any dump file generated for the mismatch.
> Here are the steps i followed,
> Started fio and waited till 30 % writes done the disk and issued a dd
> write on the same disc for the first 512 bytes with pattern zero.
> then waited till verify gets completed.
> I can see the error's in the output log file but not the dump file.
> 
> Here is my job file.
> 
> [global]
> size=10g
> direct=1
> filename=/dev/sdc
> verify_pattern=0x01010101
> verify=meta
> bs=64k
> group_reporting
> 
> [write-phase]
> rw=write
> do_verify=0
> 
> [verify-phase]
> stonewall
> rw=read
> do_verify=1
> continue_on_error=all
> verify_dump=1
> ~
> 
> 
> 
> Let me know if i am missing something over here.

You don't get the .received and .expected files?

> 2)Also i have one query like verify_pattern option is it possible to
> provide known pattern for write and reads this will be very useful in
> DI verification test cases

Not sure I understand this one. You are already providing the pattern
you want. What am I missing?

-- 
Jens Axboe


  reply	other threads:[~2012-04-06  0:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05 23:20 query on verify_dump option Suresh Dhanarajan
2012-04-06  0:16 ` Jens Axboe [this message]
2012-04-06  0:28   ` Suresh Dhanarajan
2012-04-11 20:03     ` Jens Axboe
2015-06-25  5:29       ` Alireza Haghdoost

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=4F7E35F2.5010701@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=sureshdrajan@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