linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <bmr@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: Mike Snitzer <snitzer@redhat.com>,
	Christoph Hellwig <hch@infradead.org>,
	Jens Axboe <axboe@kernel.dk>, Shaohua Li <shli@fusionio.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jeff Moyer <jmoyer@redhat.com>
Subject: Re: [dm-devel] [PATCH 1/1] block: rework flush sequencing for blk-mq
Date: Mon, 17 Mar 2014 11:55:18 +0000	[thread overview]
Message-ID: <5326E2A6.4080405@redhat.com> (raw)
In-Reply-To: <20140314141301.GA13112@redhat.com>

On 03/14/2014 02:13 PM, Mike Snitzer wrote:
> Yeah, not sure why single path scsi_debug "just works", maybe it is a
> "feature" of the older multipathd I have kicking around?, but for basic
> data path testing scsi_debug is a quick means to an end.  I can look
> closer at _why_ it gets multipathd in a bit.  But maybe Ben or Hannes
> will have quicker insight?

Do you have find_multipaths set in multipath.conf? It defaults to off.
If it's enabled then multipath will only create maps for WWIDs it
already knows about (listed in /etc/multipath/wwids) unless there are at
least two devices with the same WWID or the user forces the operation:

Mar 17 12:26:50 | checking if sdm should be multipathed
Mar 17 12:26:50 | wwid 35333333000000000 not in wwids file, skipping sdm

Turn it off and multipath will happily map a single path scsi_debug for me:

# multipath
create: mpathg (35333333000000000) undef Linux,scsi_debug
size=1.0G features='0' hwhandler='0' wp=undef
`-+- policy='round-robin 0' prio=1 status=undef
  `- 8:0:0:0 sdm 8:192 undef ready  running

Iirc this is enabled on at least some current distros by default to
avoid creating maps for USB keys and the like.

Regards,
Bryn.


      parent reply	other threads:[~2014-03-17 11:55 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30 13:26 [PATCH 0/1] block: rework flush sequencing for blk-mq Christoph Hellwig
2014-01-30 13:26 ` [PATCH 1/1] " Christoph Hellwig
2014-02-07  1:18   ` Shaohua Li
2014-02-07 14:19     ` Christoph Hellwig
2014-02-08  0:55       ` Shaohua Li
2014-02-10 10:33         ` Christoph Hellwig
2014-03-07 20:45   ` Jeff Moyer
2014-03-08 15:52     ` Christoph Hellwig
2014-03-08 17:33       ` Mike Snitzer
2014-03-08 19:51         ` Hannes Reinecke
2014-03-08 18:13           ` Mike Snitzer
2014-03-08 21:33             ` Hannes Reinecke
2014-03-08 22:09               ` [PATCH] block: fix q->flush_rq NULL pointer crash on dm-mpath flush Mike Snitzer
2014-03-09  0:24                 ` Jens Axboe
2014-03-09  0:57                   ` Mike Snitzer
2014-03-09  3:18                     ` Jens Axboe
2014-03-09  3:29                       ` Mike Snitzer
2014-03-12 10:28           ` [PATCH 1/1] block: rework flush sequencing for blk-mq Christoph Hellwig
2014-03-12 10:50             ` Hannes Reinecke
2014-03-12 10:55               ` Christoph Hellwig
2014-03-12 11:07                 ` Hannes Reinecke
2014-03-12 11:00               ` SuSE O_DIRECT|O_NONBLOCK overload Christoph Hellwig
2014-03-13  0:15                 ` NeilBrown
2014-03-14 17:46                   ` Mike Christie
2014-03-13 16:13             ` [PATCH 1/1] block: rework flush sequencing for blk-mq Mike Snitzer
2014-03-14  9:25               ` Christoph Hellwig
2014-03-14  9:30                 ` Hannes Reinecke
2014-03-14 12:44                   ` Christoph Hellwig
2014-03-14  9:34                 ` Christoph Hellwig
2014-03-14  9:52                   ` Hannes Reinecke
2014-03-14 10:58                     ` Christoph Hellwig
2014-03-14 11:10                       ` Hannes Reinecke
2014-03-14 13:00                 ` Mike Snitzer
2014-03-14 13:23                   ` Christoph Hellwig
2014-03-14 14:13                     ` Mike Snitzer
2014-03-15 13:28                       ` scsi_debug and mutipath, was " Christoph Hellwig
2014-03-17 11:55                       ` Bryn M. Reeves [this message]

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=5326E2A6.4080405@redhat.com \
    --to=bmr@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=dm-devel@redhat.com \
    --cc=hch@infradead.org \
    --cc=jmoyer@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shli@fusionio.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 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).