From: Martin Wilck <mwilck@suse.com>
To: "Xose Vazquez Perez" <xose.vazquez@gmail.com>,
"Tom Geng(耿芳忠)" <gengfangzhong@inspur.com>
Cc: "dm-devel@redhat.com" <dm-devel@redhat.com>
Subject: Re: multipath-tools: add INSPUR/MCS to hardware table
Date: Tue, 30 Jan 2018 15:05:52 +0100 [thread overview]
Message-ID: <1517321152.4072.46.camel@suse.com> (raw)
In-Reply-To: <304d593e-b9ba-3c19-fae0-084caa0e1a97@gmail.com>
On Tue, 2018-01-30 at 14:58 +0100, Xose Vazquez Perez wrote:
> On 01/29/2018 02:37 PM, Martin Wilck wrote:
>
> > On Mon, 2018-01-29 at 06:04 +0000, Tom Geng(耿芳忠) wrote:
> > > + /*
> > > + * INSPUR
> > > + */
> > > + {
> > > + /* AS5300/AS5500 G2 */
> > > + .vendor = "INSPUR",
> > > + .product = "MCS",
> > > + .pgpolicy = GROUP_BY_PRIO,
>
> ^^^^^^^^ ^^^^^^^^^^^^^
>
> > > + .pgfailback = -FAILBACK_IMMEDIATE,
> > > + .prio_name = PRIO_ALUA,
> > > + },
> > multipath-tools default to .pgpolicy = failover. Please confirm
> > that
> > this is really your intention.
>
> It was set as GROUP_BY_PRIO, with PRIO_ALUA as prio.
Argh. Obvious case of brain malfunction on my part. Sorry, everyone.
Martin
--
Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2018-01-30 14:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 6:04 multipath-tools: add INSPUR/MCS to hardware table Tom Geng(耿芳忠)
2018-01-29 13:37 ` Martin Wilck
2018-01-30 1:54 ` Tom Geng(耿芳忠)
2018-01-30 7:33 ` Martin Wilck
2018-01-30 13:58 ` Xose Vazquez Perez
2018-01-30 14:05 ` Martin Wilck [this message]
2018-01-30 18:13 ` Xose Vazquez Perez
-- strict thread matches above, loose matches on Subject: below --
2018-01-23 11:01 Tom Geng(耿芳忠)
2018-01-22 10:55 Tom Geng(耿芳忠)
2018-01-22 14:44 ` 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=1517321152.4072.46.camel@suse.com \
--to=mwilck@suse.com \
--cc=dm-devel@redhat.com \
--cc=gengfangzhong@inspur.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).