All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <bmr@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Can DM-Multipath work on non-SCSI block device
Date: Thu, 14 Mar 2013 10:41:12 +0000	[thread overview]
Message-ID: <5141A948.3010403@redhat.com> (raw)
In-Reply-To: <51419874.50308@suse.de>

On 03/14/2013 09:29 AM, Hannes Reinecke wrote:
> On 03/14/2013 08:58 AM, Ahmed Al-Mehdi wrote:
>> Hello,
>>
>> I read the documentation on the dm-multipath home page:
>> htttp://christophe.varoqui.free.fr/refbook.html
>> <http://christophe.varoqui.free.fr/refbook.html> , that describes
>> how the userspace multipath tool detects and maps (scsi) devices.
>> However, would like to confirm, does the dm-multipath utilty only
>> work with SCSI devices.  Is there any option to make it (or fake it)
>> to work with non-SCSI  block device.
>>
> If you can figure out a way on how to get a unique _disk_ id without
> SCSI, sure.

E.g. cciss devices are supported using the cciss_id program - that's a 
good example of a very "non-scsi" device type working with multipath.

As well as the WWID problem you'll need to come up with some scheme for 
faking unique HCIL values for the devices since multipath userspace 
cares about that. The cciss approach is to force lun and channel to '0' 
for all devices and to use the CCISS controller (cN) and disk (dN) 
values for the host and id (aka target) values.

See the functions in discovery.c with a cciss_ prefix for more examples.

Regards,
Bryn.

  reply	other threads:[~2013-03-14 10:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-14  7:58 Can DM-Multipath work on non-SCSI block device Ahmed Al-Mehdi
2013-03-14  9:29 ` Hannes Reinecke
2013-03-14 10:41   ` Bryn M. Reeves [this message]
2013-03-14 10:44     ` Hannes Reinecke

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=5141A948.3010403@redhat.com \
    --to=bmr@redhat.com \
    --cc=dm-devel@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.