linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Junichi Nomura <j-nomura@ce.jp.nec.com>
Cc: device-mapper development <dm-devel@redhat.com>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: dm-multipath test scripts
Date: Thu, 18 Feb 2016 12:17:45 -0500	[thread overview]
Message-ID: <20160218171745.GA15071@redhat.com> (raw)
In-Reply-To: <20151007053923.GA10749@xzibit.linux.bs1.fc.nec.co.jp>

On Wed, Oct 07 2015 at  1:39am -0400,
Junichi Nomura <j-nomura@ce.jp.nec.com> wrote:

> This is a set of scripts for kernel-side dm-multipath testing. Current
> set of scripts are stress testing of extreme situation and its coverage
> is limited. But recently found dm-mpath regressions should be detectable
> with this. I hope this helps people working on dm-multipath related code
> as a regression test set.
> 
> Though this is created as a patch for linux kernel source, it's just for
> convenience of kernel developers (I don't have a place to host this kind
> of scripts). If there are better place to contribute this, please let me know.
> 
> Please check README for how-to-run and possible improvements you could
> contribute in future.

I finally got around to trying these scripts.  Thanks for making them
available.

But unfortunately I cannot get either the scsidebug or tcmloop mode to
run against v4.5-rc4

For tcmloop, targetcli fails with:
"Could not create ISCSIFabricModule in configFS."
(fixed by enabling CONFIG_ISCSI_TARGET under TARGET_CORE)

I'm seeing all tests fail due to fio verification failure.  I'll need to
inspect this further..

But the most problematic test is ./tests/test_03_dm_failpath -- it seems
to actively break _any_ v4.5-rc kernel I try (with a never-ending flood
of messages like "device-mapper: multipath: Failing path 8:192."); I
haven't tried older kernels.

What is the last kernel version that your scripts have worked on?

Taking a step back:
These scripts don't belong in Documentation/device-mapper/mptest/ (or
anywhere in the kernel tree for that matter).

I'd really prefer it if we could port your scripts over to the
device-mapper-test-suite, see:
https://github.com/jthornber/device-mapper-test-suite

Mike

  parent reply	other threads:[~2016-02-18 17:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-07  5:39 dm-multipath test scripts Junichi Nomura
2015-10-07  7:31 ` Johannes Thumshirn
2015-10-08 23:10   ` Junichi Nomura
2015-11-13 10:55 ` Johannes Thumshirn
2015-11-14 16:26   ` Mike Snitzer
2016-02-18 17:17 ` Mike Snitzer [this message]
2016-02-19  0:33   ` Junichi Nomura
2016-02-19  8:37     ` Junichi Nomura
2016-02-19 19:42       ` Mike Snitzer
2016-02-20  6:12         ` Mike Snitzer
2016-02-20  9:42           ` Hannes Reinecke
2016-02-20 15:13             ` [dm-devel] " Bart Van Assche
2016-02-20 16:34             ` Mike Snitzer
2016-02-22  9:51           ` Junichi Nomura
2016-02-22 15:09             ` why is blk-mq requeue foricbly kicking stopped queues? [was: Re: dm-multipath test scripts] Mike Snitzer
2016-02-23  1:34               ` Junichi Nomura
2016-02-23  3:43                 ` Mike Snitzer
2016-02-24 19:37     ` dm-multipath test scripts Mike Snitzer

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=20160218171745.GA15071@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=j-nomura@ce.jp.nec.com \
    --cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).