Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Karthick Srinivasachary <karthick@pernixdata.com>
Cc: fio@vger.kernel.org
Subject: Re: Repeat given pattern with buffer_compress_percentage
Date: Fri, 05 Dec 2014 10:20:25 -0700	[thread overview]
Message-ID: <5481E959.8020402@kernel.dk> (raw)
In-Reply-To: <5481E539.3000806@kernel.dk>

On 12/05/2014 10:02 AM, Jens Axboe wrote:
> On 12/05/2014 12:25 AM, Karthick Srinivasachary wrote:
>> Hi Jens,
>>
>> Awesome.. Thanks for the fix..!
>> With compress_percentage 80 or more, fio verify is failing. I don't
>> think there any issue with storage in my test environment. Do you
>> think we have a bug here. Complete command and output below.
>>
>> /usr/local/bin/fio --name=global --ioengine=libaio --bsrange=16k-64k
>> --rw=randrw --iodepth=16 --direct=1 --verify=md5 --name=job0
>> --size=100m --filename=/fio/fio.dat --rw=randrw --rate=20m
>> --buffer_compress_percentage=80 --refill_buffers --buffer_pattern=123
>> --verify_dump=1
>
> You can't do a random read/write test, it'll fail on the reads that have
> not been populated. It might sometimes work if the file had been laid
> out prior with the right contents, but generally you cannot depend upon
> it. You want to do just --rw=randwrite and then the verify phase will
> take place after the writes are done, verifying those.
>
> Try and delete fio.dat prior to running this job, and it should fail
> consistently with or without buffer_compress_percentage.

I take it back, there is a bug there. Fio does skip verifying the reads 
we generate initially, and verifies the written data after the 
read/write phase. So it _should_ work, the fact that it doesn't is a 
bug. I'll take a look at it.

-- 
Jens Axboe



  reply	other threads:[~2014-12-05 17:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03 18:48 Repeat given pattern with buffer_compress_percentage Karthick Srinivasachary
2014-12-03 19:45 ` Andrey Kuzmin
2014-12-03 19:49   ` Karthick Srinivasachary
2014-12-03 19:52     ` Andrey Kuzmin
2014-12-04  2:42 ` Jens Axboe
2014-12-04  2:49   ` Jens Axboe
2014-12-04  2:58     ` Jens Axboe
2014-12-04  7:53       ` Karthick Srinivasachary
2014-12-04 15:27         ` Jens Axboe
2014-12-04 22:41           ` Jens Axboe
2014-12-05  7:25             ` Karthick Srinivasachary
2014-12-05 17:02               ` Jens Axboe
2014-12-05 17:20                 ` Jens Axboe [this message]
2014-12-05 17:46                   ` Jens Axboe
2014-12-05 20:06                     ` Karthick Srinivasachary

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=5481E959.8020402@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=karthick@pernixdata.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