Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Wallence Lu <wallencelu@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: A bug in combining fsrange and verify
Date: Mon, 27 Jan 2014 15:46:03 -0700	[thread overview]
Message-ID: <20140127224603.GM2782@kernel.dk> (raw)
In-Reply-To: <CAOpYm_WNfhkyFRofHg6aUfm_nxL7oX8gCc++wNFMproqP1rVeA@mail.gmail.com>

On Mon, Jan 27 2014, Wallence Lu wrote:
> Recreated with fio 2.0.11-35-g8428, the version was checked out from
> https://github.com/axboe/fio.

2.1.4 is the latest, but I don't think that would change anything for
you.

> I read a little bit of the source code, it seems to me the randwrite
> option gets the LBA without specifying the IO size. With that said,
> for a bsrange option, it is likely one random IO can step onto another
> IO if they happen to be adjacent. For example, request A has LBA
> of 1024 and size 8K, request B has LBA 1016 and size 16K. Without
> checking the request size, request B can overwrite content of request
> A.
> 
> Is that the right interpretation? Do I miss something? Thanks.

Fio is supposed to handle that, the job file should work. I'll take a
look at it.

-- 
Jens Axboe


  reply	other threads:[~2014-01-27 22:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-25  2:07 A bug in combining fsrange and verify Wallence Lu
2014-01-27 19:22 ` Jens Axboe
2014-01-27 20:42   ` Wallence Lu
2014-01-27 22:46     ` Jens Axboe [this message]
2014-01-27 23:03       ` Jens Axboe
2014-01-27 23:16         ` Grant Grundler
2014-01-27 23:31           ` Jens Axboe
2014-01-28  0:00             ` Grant Grundler
2014-01-28 17:26               ` Jens Axboe
2014-02-03 22:05                 ` Grant Grundler

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=20140127224603.GM2782@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=wallencelu@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