From: Bart Van Assche <bvanassche@acm.org>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Jun'ichi Nomura <j-nomura@ce.jp.nec.com>,
device-mapper development <dm-devel@redhat.com>
Subject: Re: v3.15 dm-mpath regression: cable pull test causes I/O hang
Date: Thu, 03 Jul 2014 16:34:09 +0200 [thread overview]
Message-ID: <53B569E1.1010405@acm.org> (raw)
In-Reply-To: <20140703140516.GB28104@redhat.com>
On 07/03/14 16:05, Mike Snitzer wrote:
> How easy would it be to replicate your testbed? Is it uniquely FIO hw
> dependent? How are you simulating the cable pull tests?
>
> I'd love to setup a testbed that would enable me to chase this more
> interactively rather than punting to you for testing.
Hello Mike,
The only nonstandard hardware that is required to run my test is a pair
of InfiniBand HCA's and an IB cable to connect these back-to-back. The
test I ran is as follows:
* Let an SRP initiator log in to an SRP target system.
* Start multipathd and srpd.
* Start a fio data integrity test on the initiator system on top of
/dev/dm-0.
* From the target system simulate a cable pull by disabling IB traffic
via the ibportstate command.
* After a random delay, unload and reload SCST and the IB stack. This
makes the IB ports operational again.
* After a random delay, repeat the previous two steps.
If you want I can send you the scripts I use to run this test and also
the instructions that are necessary to build and install the SCST SRP
target driver.
Bart.
next prev parent reply other threads:[~2014-07-03 14:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 13:02 v3.15 dm-mpath regression: cable pull test causes I/O hang Bart Van Assche
2014-06-27 13:33 ` Mike Snitzer
2014-06-27 14:18 ` Bart Van Assche
2014-07-02 22:02 ` Mike Snitzer
2014-07-03 5:43 ` Hannes Reinecke
2014-07-03 13:56 ` Bart Van Assche
2014-07-03 13:58 ` Hannes Reinecke
2014-07-03 14:05 ` Mike Snitzer
2014-07-03 14:15 ` Hannes Reinecke
2014-07-03 14:18 ` Mike Snitzer
2014-07-03 14:34 ` Bart Van Assche [this message]
2014-07-03 15:00 ` Mike Snitzer
2014-07-07 13:28 ` Bart Van Assche
2014-07-04 3:10 ` Junichi Nomura
2014-07-07 13:40 ` Bart Van Assche
2014-07-08 0:55 ` Junichi Nomura
2014-07-08 9:43 ` Bart Van Assche
2014-07-08 16:33 ` Mike Snitzer
2014-07-08 23:24 ` Junichi Nomura
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=53B569E1.1010405@acm.org \
--to=bvanassche@acm.org \
--cc=dm-devel@redhat.com \
--cc=j-nomura@ce.jp.nec.com \
--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.