From: Jens Axboe <axboe@kernel.dk>
To: Sitsofe Wheeler <sitsofe@gmail.com>
Cc: fio <fio@vger.kernel.org>
Subject: Re: server mode and verify_dump
Date: Fri, 14 Aug 2015 13:22:41 -0600 [thread overview]
Message-ID: <55CE4001.8090705@kernel.dk> (raw)
In-Reply-To: <CALjAwxhbjE4xTZ5jA_m-0spFTtvwJb_bNZz7m7cPRcCXLY1wNA@mail.gmail.com>
On 08/14/2015 01:21 PM, Sitsofe Wheeler wrote:
> On 14 August 2015 at 20:17, Jens Axboe <axboe@kernel.dk> wrote:
>> Right, I suspected that might have been the case. If the header isn't valid,
>> then fio doesn't dump any contents. One could argue that it would be cleaner
>
> What do you think it would take to dump a block's worth of data when
> encountering a header error during a verify?
Without a valid header, we can't re-generate the data. That's why it
currently doesn't dump the expected contents if the header verification
fails.
--
Jens Axboe
next prev parent reply other threads:[~2015-08-14 19:22 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
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 [this message]
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=55CE4001.8090705@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