From: Jens Axboe <jens.axboe@oracle.com>
To: "Ricardo M. Correia" <Ricardo.M.Correia@Sun.COM>
Cc: fio@vger.kernel.org
Subject: Re: Bad verify header
Date: Tue, 23 Feb 2010 10:38:33 +0100 [thread overview]
Message-ID: <20100223093833.GR1025@kernel.dk> (raw)
In-Reply-To: <1266458472.19149.83.camel@cfslap.wizy.org>
On Thu, Feb 18 2010, Ricardo M. Correia wrote:
> Ok, this one appears to be because of the 'bsrange' option.
>
> It works fine if I replace that option by 'bs=512' or 'bs=128k'.
>
> Any chance of this problem being fixed, or is the 'verify' option
> conceptually incompatible with 'bsrange'?
If I recall correctly, it's due to overlaps of the ios screwing up the
verify headers. It's not impossible to fix, but you have to either relax
the IO coverage or make the random block generator more clever (so eg
once a 512b block has been allocated, you can only fit < 128KB blocks
into the remaining offsets).
--
Jens Axboe
prev parent reply other threads:[~2010-02-23 9:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 1:48 Bad verify header Ricardo M. Correia
2010-02-18 2:01 ` Ricardo M. Correia
2010-02-23 9:38 ` 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=20100223093833.GR1025@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=Ricardo.M.Correia@Sun.COM \
--cc=fio@vger.kernel.org \
/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