All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: "McIntyre, Vincent (CASS, Marsfield)" <Vincent.Mcintyre@csiro.au>,
	"dm-devel@redhat.com" <dm-devel@redhat.com>
Subject: Re: Promise and ALUA
Date: Thu, 13 Aug 2020 22:07:49 +0200	[thread overview]
Message-ID: <8c910ecb-ddf8-0a91-4310-4daedb85cd89@gmail.com> (raw)
In-Reply-To: <20200810043316.GH21810@mayhem.atnf.CSIRO.AU>

On 8/10/20 6:33 AM, McIntyre, Vincent (CASS, Marsfield) wrote:

> for many years we have been operating some Promise VTrak arrays
> without any use of the ALUA feature (largely so we don't have to
> specify LUN affinities as well, which seems to be required).
> 
> In the process of upgrading to Debian Buster
> (multipath-tools 0.7.9 and kernel 4.19)
> I find that I can no longer connect to our Promise arrays.
> They are detected but the only useful output I get is
> 
>   multipathd[986]: reconfigure (operator)
>   multipathd[986]: sdc: alua not supported
>   multipathd[986]: sdd: alua not supported
>   multipathd[986]: sdr: alua not supported
>   multipathd[986]: sde: alua not supported
>   multipathd[986]: sdf: alua not supported
>   multipathd[986]: sdg: alua not supported
>   multipathd[986]: sdh: alua not supported
>   multipathd[986]: sdi: alua not supported
> 
> 
> I found the note in the manpage about alua being selected by
> default for these arrays[1], but I'm taken aback that I'm not
> allowed to override this.
> 
> Is there really no support any more for choosing whether to use
> ALUA or not?
> 
> I have tried messing about with detect_prio, dectect_checker
> and whatnot, to no avail.

> [1] 9b5ea2eda85ae072cb697310807611c693713c2b
>      libmultipath: retain_attached_hw_handler obsolete with 4.3+

With the next array config and an empty /etc/multipath.conf,
reboot the linux host and put the output of "multipath -ll"
Redundancy Type: Active-Active
LUN Affinity: Enable
ALUA: Enable

  reply	other threads:[~2020-08-13 20:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10  4:33 Promise and ALUA McIntyre, Vincent (CASS, Marsfield)
2020-08-13 20:07 ` Xose Vazquez Perez [this message]
2020-08-13 23:51   ` McIntyre, Vincent (CASS, Marsfield)
2020-08-14  0:24     ` Xose Vazquez Perez
2020-08-14  2:18       ` McIntyre, Vincent (CASS, Marsfield)
2020-08-15 20:36         ` Xose Vazquez Perez
2020-08-16  2:30           ` McIntyre, Vincent (CASS, Marsfield)
2020-08-16  3:50             ` Xose Vazquez Perez

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=8c910ecb-ddf8-0a91-4310-4daedb85cd89@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=Vincent.Mcintyre@csiro.au \
    --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.