From: Martin Wilck <mwilck@suse.com>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: Matthias Rudolph <Matthias.Rudolph@hitachivantara.com>,
DM-DEVEL ML <dm-devel@redhat.com>
Subject: Re: [dm-devel] [PATCH] multipath-tools: adapt HITACHI/OPEN- config to work with alua and multibus
Date: Mon, 05 Jun 2023 11:39:11 +0200 [thread overview]
Message-ID: <d4bc81d4631a7b487e88314f18f6877541dc5121.camel@suse.com> (raw)
In-Reply-To: <8a1a8cb2-565c-6647-0424-548eaca34a78@gmail.com>
On Sat, 2023-06-03 at 13:12 +0200, Xose Vazquez Perez wrote:
> On 5/31/23 17:49, Martin Wilck wrote:
>
> > On Wed, 2023-05-31 at 15:57 +0200, Xose Vazquez Perez wrote:
> > > ALUA is needed by Hitachi Global-Active Device (GAD):
> > > https://knowledge.hitachivantara.com/Documents/Management_Software/SVOS/8.1/Global-Active_Device/Overview_of_global-active_device
>
> > Thanks, but where exactly did you find this information in the
> > linked
> > document? I don't see ALUA mentioned. Unfortunately Hitachi chose
> > to
> > use non-standard terminology...
>
> No public info, personal e-mail from Matthias:
>
> "We have also a config for ALUA. It is used for hardware copy between
> two
> arrays and the server should only use the local paths:
>
> SLES 12 SP2 ALUA:
>
> device {
> vendor "HITACHI"
> product "OPEN-.*"
> features "0"
> path_grouping_policy group_by_prio
> prio alua
> path_selector "round-robin 0"
> rr_weight uniform
> no_path_retry 1
> rr_min_io 100
> path_checker directio
> failback immediate
> }
> "
>
> > Is ALUA always active / supported in these arrays?
>
> Disable by default. And it is only needed with GAD setup:
>
> Array settings:
> "ALUA Mode" Enabled
> "Path Mode" ALUA
> "ALUA Permitted" YES
> "ALUA Settable" YES
> "Target Port Asymmetric Access State" Active/Optimized
>
> Same case as HUAWEI
> https://github.com/opensvc/multipath-tools/commit/9283fa6663ad908fd0419edcef4795fbbbe9f09d
>
> "no_path_retry 10" comes from:
> https://knowledge.hitachivantara.com/Documents/Management_Software/SVOS/9.8.6/Volume_Management_-_VSP_5000_Series/Host_Attachment/05_Red_Hat_Linux_configuration_and_attachment#Device_Mapper_(DM)_Multipath_configuration.0D.0A____for_Red_Hat_Linux
Thanks a lot. I'll apply your patch, adding part of this information to
the commit message.
Martin
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2023-06-05 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 13:57 [dm-devel] [PATCH] multipath-tools: adapt HITACHI/OPEN- config to work with alua and multibus Xose Vazquez Perez
2023-05-31 15:49 ` Martin Wilck
2023-06-03 11:12 ` Xose Vazquez Perez
2023-06-05 9:39 ` Martin Wilck [this message]
2023-06-05 9:38 ` Martin Wilck
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=d4bc81d4631a7b487e88314f18f6877541dc5121.camel@suse.com \
--to=mwilck@suse.com \
--cc=Matthias.Rudolph@hitachivantara.com \
--cc=dm-devel@redhat.com \
--cc=xose.vazquez@gmail.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).