From: Jens Axboe <axboe@kernel.dk>
To: Steven Lang <tirea@google.com>
Cc: fio@vger.kernel.org
Subject: Re: [PATCH] Expand continue_on_error to select which type of error to allow
Date: Thu, 17 Nov 2011 09:45:46 +0100 [thread overview]
Message-ID: <4EC4C9BA.2090905@kernel.dk> (raw)
In-Reply-To: <CAAUT-yMXe=PK1roL710ciSqZqqnh2GSmGb6BVyUMreY5Yqbwbw@mail.gmail.com>
On 2011-11-17 04:09, Steven Lang wrote:
> This expands the continue_on_error option to take a string specifying
> what type of error to continue on, breaking out errors into read,
> write, and verify. (Sync, trim, and anything else not specifically a
> read are considered write operations for the sake of error
> continuation.)
>
> Backwards compatibility is retained by allowing =0 and =1 values to
> specify none and all, respectively.
Thanks, this is a good idea. I have applied it. Can I talk you into also
sending in an update for the fio.1 man page?
--
Jens Axboe
prev parent reply other threads:[~2011-11-17 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 3:09 [PATCH] Expand continue_on_error to select which type of error to allow Steven Lang
2011-11-17 8:45 ` 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=4EC4C9BA.2090905@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=tirea@google.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