Linux Device Mapper development
 help / color / mirror / Atom feed
From: Sebastian Herbszt <herbszt@gmx.de>
To: dm-devel@redhat.com
Cc: Sebastian Herbszt <herbszt@gmx.de>
Subject: Status of SCSI referrals support in dm-multipath
Date: Sun, 1 Jun 2014 22:46:50 +0200	[thread overview]
Message-ID: <20140601224650.000043de@localhost> (raw)

Hello,

I am trying to find out the status of SCSI referrals support in dm-multipath.
SCSI referrals support was a topic at LSF [1] but I wasn't able to find any
information. Back in 2010 Hannes suggested the use of multiple entries in a
multipath table [2] but this doesn't seem to work (anymore):

[ 7750.354190] device-mapper: table: Request-based dm doesn't support multiple targets yet

Is there any SCSI referrals support yet?

[1] http://marc.info/?l=linux-scsi&m=129553880112460&w=2
[2] http://www.redhat.com/archives/dm-devel/2010-June/msg00155.html

Sebastian

             reply	other threads:[~2014-06-01 20:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-01 20:46 Sebastian Herbszt [this message]
2014-06-02  6:34 ` Status of SCSI referrals support in dm-multipath Hannes Reinecke
2014-07-27 22:18   ` Sebastian Herbszt

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=20140601224650.000043de@localhost \
    --to=herbszt@gmx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox