Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Gwendal Grignou <gwendal@chromium.org>
Cc: Puthikorn Voravootivat <puthik@chromium.org>, fio@vger.kernel.org
Subject: Re: [fio-2.1.9] verify and bssplit do not work together
Date: Mon, 21 Jul 2014 22:30:44 +0200	[thread overview]
Message-ID: <53CD7874.7010203@kernel.dk> (raw)
In-Reply-To: <CAMHSBOV1Vm4Ds1th+OB-JQ6h7kiN8VKR9E4+7aiiN2F=fbjVaw@mail.gmail.com>

On 2014-07-21 22:24, Gwendal Grignou wrote:
> Jens,
>   I still see some verify errors when I set 'experimental_verify=1'
>
> verify: bad magic header 977c, wanted acca at file /tmp/test offset
> 15478784, length 429437046
> verify: bad magic header 8aac, wanted acca at file /tmp/test offset
> 28082176, length 302426815
> verify: bad magic header c8ad, wanted acca at file /tmp/test offset
> 30408704, length 318473336
> verify: bad magic header 3791, wanted acca at file /tmp/test offset
> 65024000, length 74750452
>
> However, without this line, there are no verify errors anymore.
>
> The fio file is:
> [stress]
> filename=/tmp/test
> size=107374182
>
> readwrite=randrw
> bssplit=4k/50:1M/50
> ;bs=64k
>
> do_verify=1
> experimental_verify=1
> verify=meta
> verify_interval=64k
> verify_dump=1
> continue_on_error=verify

I'll look into the experimental_verify bit - there's a reason it's 
experimental :-). But the hope is to make that the method for 
verification, so I'll look into what goes wrong there. It might be 
highlighting problems elsewhere (like accidental overwrites, due to the 
mixed block sizes).

-- 
Jens Axboe



      reply	other threads:[~2014-07-21 20:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17 20:36 [fio-2.1.9] verify and bssplit do not work together Gwendal Grignou
2014-07-18  7:47 ` Jens Axboe
2014-07-21  8:29   ` Jens Axboe
2014-07-21 17:41     ` Gwendal Grignou
2014-07-21 17:49     ` Gwendal Grignou
2014-07-21 18:40       ` Jens Axboe
2014-07-21 18:52         ` Jens Axboe
2014-07-21 20:24           ` Gwendal Grignou
2014-07-21 20:30             ` 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=53CD7874.7010203@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=gwendal@chromium.org \
    --cc=puthik@chromium.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