Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Radha Ramachandran <radha@google.com>
Cc: fio@vger.kernel.org
Subject: Re: Disabling verify when norandommap is given
Date: Thu, 19 Feb 2009 08:47:13 +0100	[thread overview]
Message-ID: <20090219074712.GD30821@kernel.dk> (raw)
In-Reply-To: <66dfd3fe0902181512o5a88da43waaf09834bd6d37ac@mail.gmail.com>

On Wed, Feb 18 2009, Radha Ramachandran wrote:
> Hi,
> Is there a reason why there is a hard rule to disable verify when
> norandommap option is also set?

Without a map of the blocks that have been written already, you might
overwrite full or partial blocks before you are done. That would cause
verify to fail. See the 'norandommap' explanation in the HOWTO as well.

-- 
Jens Axboe


  reply	other threads:[~2009-02-19  7:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-18 23:12 Disabling verify when norandommap is given Radha Ramachandran
2009-02-19  7:47 ` Jens Axboe [this message]
2009-02-19 18:10   ` Radha Ramachandran
2009-02-19 18:26     ` Jens Axboe
2009-02-19 19:56       ` Radha Ramachandran
2009-02-19 20:12         ` Jens Axboe

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=20090219074712.GD30821@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=fio@vger.kernel.org \
    --cc=radha@google.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