From: Hannes Reinecke <hare@suse.de>
To: device-mapper development <dm-devel@redhat.com>
Cc: tony.lapointe@connexim.ca, daniel.milani@connexim.ca
Subject: Re: multipath-tools with STK FLEXLINE 380
Date: Wed, 22 Nov 2006 16:29:16 +0100 [thread overview]
Message-ID: <45646CCC.3070601@suse.de> (raw)
In-Reply-To: <1164132148.2066.19.camel@localhost.localdomain>
Tony Lapointe wrote:
> Do not use 'rr_weight=priorities'. The priorities
> handling is currently buggered; or, put it the other way
> round, you will need at least my latest fix to get it
> working. Just remove that line and stay with the
> defaults. That should work.
>
> And as a sidenote: Using 'group_by_prio' and
> 'rr_weight=priorities' is completely pointless, even if
> 'rr_weight=priorities' should be working.'group_by_prio'
> will lump all devices with the same priority into one
> group. And 'rr_weight=priorities' will then modify the
> 'minio' based on the priority. So you can as well
> directly modify the 'minio'
> parameter.'rr_weight=priorities' only makes sense if you
> have path with different priorities in one group, ie
> when using 'multibus' or 'group_by_serial'.
> Cheers,
>
> Hannes
> --
> Dr. Hannes Reinecke hare suse de
> SuSE Linux Products GmbH S390 & zSeries
> Maxfeldstraße 5 +49 911 74053 688
> 90409 Nürnberg http://www.suse.de
>
>
>
>
> Hi Hannes,
>
> thanks for the reply.
>
> I've tried without "rr_weight=priorities" in my multipath.conf but it does
> not work either.
> The only difference it makes is that "multipath -v3" now output :
> "rr_weight = 1 (internal default)"
> instead of "rr_weight = 2 (config file default)".
>
> I was thinking that "group_by_prio" is use to group together devices with
> differents priorities, with the one with the highest priority first,
is it wrong?
>
Yes. It groups devices with _identical_ priorities together.
> The output of "multipath -d -v2" seems to reflect this :
>
[ .. ]
The output is correct. You have two paths to each disk, and each path
has a different priority. So the multipath topology is correct.
Cheers,
Hannes
--
Dr. Hannes Reinecke hare@suse.de
SuSE Linux Products GmbH S390 & zSeries
Maxfeldstraße 5 +49 911 74053 688
90409 Nürnberg http://www.suse.de
next prev parent reply other threads:[~2006-11-22 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 18:02 multipath-tools with STK FLEXLINE 380 Tony Lapointe
2006-11-22 15:29 ` Hannes Reinecke [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-16 18:03 Tony Lapointe
2006-11-20 8:07 ` Hannes Reinecke
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=45646CCC.3070601@suse.de \
--to=hare@suse.de \
--cc=daniel.milani@connexim.ca \
--cc=dm-devel@redhat.com \
--cc=tony.lapointe@connexim.ca \
/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.