All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	Mike Snitzer <snitzer@redhat.com>
Subject: Re: for-next branch and blktests/srp
Date: Thu, 06 Dec 2018 10:02:01 -0800	[thread overview]
Message-ID: <1544119321.185366.277.camel@acm.org> (raw)
In-Reply-To: <a73ef579-e4e8-f245-b203-1b52eb41af78@kernel.dk>

On Thu, 2018-12-06 at 10:48 -0700, Jens Axboe wrote:
> which would result in a non-zero exit, which should be expected for this
> test?

Hi Jens,

Test srp/002 simulates network failures while running fio on top of dm-mpath.
Since queue_if_no_path is enabled in multipath.conf dm-mpath will keep retrying
the block layer requests it receives if these requests fail due to path removal.
If fio reports "io_u error" for this test then that means that the test failed.
I haven't seen fio reporting any I/O errors for this test with any upstream
kernel that I tested in the past year or so.

Bart.

  reply	other threads:[~2018-12-06 18:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06 16:47 for-next branch and blktests/srp Bart Van Assche
2018-12-06 17:00 ` Jens Axboe
2018-12-06 17:19   ` Bart Van Assche
2018-12-06 17:28     ` Jens Axboe
2018-12-06 17:48       ` Jens Axboe
2018-12-06 18:02         ` Bart Van Assche [this message]
2018-12-06 18:08           ` Jens Axboe
2018-12-06 18:10           ` Bart Van Assche
2018-12-06 18:12             ` Jens Axboe
2018-12-06 18:16               ` Bart Van Assche
2018-12-06 20:56 ` Bart Van Assche
2018-12-06 21:04   ` Jens Axboe
2018-12-06 22:15     ` 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=1544119321.185366.277.camel@acm.org \
    --to=bvanassche@acm.org \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=snitzer@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.