From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Martin Wilck <mwilck@suse.com>, Benjamin Marzinski <bmarzins@redhat.com>
Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>,
DM_DEVEL-ML <dm-devel@lists.linux.dev>
Subject: Re: [PATCH 1/3] multipath-tools: add Acronis Cyber Infrastructure to hwtable
Date: Sun, 5 Oct 2025 20:21:40 +0200 [thread overview]
Message-ID: <df59e23f-8df1-4e4e-a610-93de7c6b5251@gmail.com> (raw)
In-Reply-To: <35c05d07d399fd56f1baa4c30c7a3447fef2d9fd.camel@suse.com>
On 9/23/25 8:22 AM, Martin Wilck wrote:
> On Mon, 2025-09-22 at 20:38 +0200, Martin Wilck wrote:
>> Not necessarily. path_group_prio_update() calculates the average of
>> the
>> path priorities in the group. With ALUA and groups of 6+ paths, an
>> optimized group with one healthy path will have a lower prio (8) than
>> a
>> non-optimized group with all healthy paths (10). In such a case it
>> could happen that multipathd switches to the non-optimized group and
>> never switches back.
>
> Sorry, this example was incorrect. Only paths in UP or GHOST states are
> counted in for the PG prio. In this example the optimized group would
> still have p = 50, and what I described would not occur.
>
> The example would be correct if the 5 non-"healthy" paths in the first
> PG were in standby aka GHOST state (resulting in p = 55 / 6 = 9). But
> that's a very different scenario, and highly theoretical.
>
>> I would suggest setting FAILBACK_IMMEDIATE instead. It's well
>> documented that FOLLOWOVER is only for cluster environments.
>
> Despite the wrong example, I still think FAILBACK_IMMEDIATE makes
> more sense as a general default. We can add a comment about the vendor
> recommendations.
I sent a new patch with that fixed.
next prev parent reply other threads:[~2025-10-05 18:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 19:41 [PATCH 0/3] multipath-tools: add new devices to hwtable Xose Vazquez Perez
2025-09-10 19:41 ` [PATCH 1/3] multipath-tools: add Acronis Cyber Infrastructure " Xose Vazquez Perez
2025-09-11 17:56 ` Benjamin Marzinski
2025-09-18 11:08 ` Xose Vazquez Perez
2025-09-22 18:38 ` Martin Wilck
2025-09-23 6:22 ` Martin Wilck
2025-10-05 18:21 ` Xose Vazquez Perez [this message]
2025-09-10 19:41 ` [PATCH 2/3] multipath-tools: add EqualLogic PS " Xose Vazquez Perez
2025-09-11 17:57 ` Benjamin Marzinski
2025-09-10 19:41 ` [PATCH 3/3] multipath-tools: add QSAN " Xose Vazquez Perez
2025-09-11 17:57 ` Benjamin Marzinski
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=df59e23f-8df1-4e4e-a610-93de7c6b5251@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=bmarzins@redhat.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@lists.linux.dev \
--cc=mwilck@suse.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.