From: Jens Axboe <axboe@kernel.dk>
To: Erwan Velu <evelu@redhat.com>, fio@vger.kernel.org
Subject: Re: Logging completed IOs only
Date: Fri, 12 Feb 2016 10:14:26 -0700 [thread overview]
Message-ID: <56BE12F2.5050207@kernel.dk> (raw)
In-Reply-To: <1499154031.27756078.1455294180577.JavaMail.zimbra@redhat.com>
On 02/12/2016 09:23 AM, Erwan Velu wrote:
> Hey,
>
> I was exchanging on the possibility to use fio to perform write test to a device and then check how does the device handled the power failure.
> I thought about using the verify options of it but I was shown that write_iolog does only log IOs that were sent to the device but not the one actually completed.
>
> What do you think about adding an option not to log the IO that were sent but completed ?
>
> That way it would be possible to track what was actually done at the time the log was written.
The verify trigger supports was intended for exactly that use case.
Looks like that did not make it into the man page (I'll fix that), but
read section 10 in the HOWTO for an introduction to how they work.
--
Jens Axboe
prev parent reply other threads:[~2016-02-12 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 16:23 Logging completed IOs only Erwan Velu
2016-02-12 17:14 ` 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=56BE12F2.5050207@kernel.dk \
--to=axboe@kernel.dk \
--cc=evelu@redhat.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