All of lore.kernel.org
 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: Sat, 20 Feb 2016 01:12:47 -0500	[thread overview]
Message-ID: <20160220061247.GA23333@redhat.com> (raw)
In-Reply-To: <20160219194216.GB21133@redhat.com>

On Fri, Feb 19 2016 at  2:42pm -0500,
Mike Snitzer <snitzer@redhat.com> wrote:

> On Fri, Feb 19 2016 at  3:37am -0500,
> Junichi Nomura <j-nomura@ce.jp.nec.com> wrote:
> 
> > On 02/19/16 09:33, Nomura Junichi wrote:
> > > On 02/19/16 02:17, Mike Snitzer wrote:
> > >> What is the last kernel version that your scripts have worked on?
> > > 
> > > v4.4 worked fine. I'll check with v4.5-rc4 when I get a machine.
> > 
> > v4.5-rc4 works fine, too.
> 
> Have you been running with blk-mq?
> Either by setting CONFIG_DM_MQ_DEFAULT or:
> echo Y > /sys/module/dm_mod/parameters/use_blk_mq
> 
> I'm seeing test_02_sdev_delete fail with blk-mq enabled.

I only see failure if I stack dm-mq ontop of old non-mq scsi devices with:

echo N > /sys/module/scsi_mod/parameters/use_blk_mq
echo Y > /sys/module/dm_mod/parameters/use_blk_mq

If I use scsi-mq for the underlying devices all works fine (been testing
the latest dm-4.6 branch though, I'll go back and try stock 4.5-rc4 just
to double check).

But this makes me think the novelty of having dm-mq support stacking on
non-blk-mq devices was misplaced.  It is a senseless config.  I'll
probably remove support for such stacking soon (next week). 

  reply	other threads:[~2016-02-20  6:12 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
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 [this message]
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=20160220061247.GA23333@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 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.