Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: fio@vger.kernel.org
Subject: Re: [PATCH] core: Actually EIO is a fatal error
Date: Fri, 21 Sep 2012 13:25:37 +0200	[thread overview]
Message-ID: <505C4EB1.4090800@kernel.dk> (raw)
In-Reply-To: <1348225456-21811-1-git-send-email-dmonakhov@openvz.org>

On 09/21/2012 01:04 PM, Dmitry Monakhov wrote:
> As soon as i understand this is just a mistype.

It's not a typo. By that logic, EILSEQ is fatal too, since it is a
verification failure of read data (so might as well have been an EIO).
Fatal, in this context, means errors that fio can recover from and
continue doing work.


-- 
Jens Axboe


  reply	other threads:[~2012-09-21 11:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21 11:04 [PATCH] core: Actually EIO is a fatal error Dmitry Monakhov
2012-09-21 11:25 ` Jens Axboe [this message]
2012-09-21 11:42   ` Dmitry Monakhov
2012-09-21 12:00     ` Jens Axboe
2012-09-21 12:13       ` Dmitry Monakhov
2012-09-21 12:20         ` Jens Axboe
2012-09-21 12:56           ` Dmitry Monakhov
2012-09-21 13:08             ` 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=505C4EB1.4090800@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=dmonakhov@openvz.org \
    --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