Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Sitsofe Wheeler <sitsofe@gmail.com>, fio <fio@vger.kernel.org>
Subject: Re: server mode and verify_dump
Date: Fri, 14 Aug 2015 09:58:29 -0600	[thread overview]
Message-ID: <55CE1025.6080009@kernel.dk> (raw)
In-Reply-To: <55CE0DA9.6050204@kernel.dk>

On 08/14/2015 09:47 AM, Jens Axboe wrote:
> On 08/03/2015 03:12 PM, Sitsofe Wheeler wrote:
>> Hi,
>>
>> I've noticed that when running fio in server mode it's not possible to
>> get a dump of using verify_dump when a verify mismatch occurs. Is it
>> possible to add a mode where the server process saves the mismatch
>> files to its current working directory for inspection later?
>
> That sounds like an oversight. To save time, can you let me know how you
> are invoking fio and with what job file? Should not be that hard to
> fixup, it should just work.

Just tested this, and the fio backend does dump the files if 
verify_dump=1 is set:

[...]
<lenny> write3: (g=0): rw=randread, bs=4K-4K/4K-4K/4K-4K, ioengine=sync, 
iodepth=1
<lenny> Starting 1 process
<lenny> crc16: verify failed at file file offset 2023424, length 4096
<lenny>        Expected CRC: 5b54
<lenny>        Received CRC: c1aa
<lenny>        received data dumped as file.2023424.received
<lenny>        expected data dumped as file.2023424.expected


-- 
Jens Axboe



  reply	other threads:[~2015-08-14 15:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 21:12 server mode and verify_dump Sitsofe Wheeler
2015-08-14 15:47 ` Jens Axboe
2015-08-14 15:58   ` Jens Axboe [this message]
2015-08-14 19:11     ` Sitsofe Wheeler
2015-08-14 19:17       ` Jens Axboe
2015-08-14 19:21         ` Sitsofe Wheeler
2015-08-14 19:22           ` Jens Axboe
2015-08-14 19:41             ` Sitsofe Wheeler
2015-08-14 19:50               ` 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=55CE1025.6080009@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=sitsofe@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