All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Wilck <mwilck@suse.com>
To: Christophe Varoqui <christophe.varoqui@opensvc.com>
Cc: dm-devel@redhat.com
Subject: Re: [PATCH 1/2] libmultipath: fallback to const prio if getprio() fails
Date: Tue, 20 Mar 2018 22:13:24 +0100	[thread overview]
Message-ID: <1521580404.3798.175.camel@suse.com> (raw)
In-Reply-To: <20180320165010.15259-1-mwilck@suse.com>

On Tue, 2018-03-20 at 17:50 +0100, Martin Wilck wrote:
> Some storage controllers don't support ALUA even though they have
> hwtable entries telling so. One such example is the IBM IPR SAS
> controller
> found on certain IBM Power systems. IBM has confirmed that reliable
> detection of ALUA support for this controller by vendor/model/rev is
> impossible.
> 
> For such cases, instead of simply failing to setup multipath, fall
> back
> to const prio.
> 
> Signed-off-by: Martin Wilck <mwilck@suse.com>

NACK to self. I just realized that this won't work, because we might be
resetting e.g. alua prioritizer to "const" because of a temporary
problem. So this needs more thought.

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

      parent reply	other threads:[~2018-03-20 21:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20 16:50 [PATCH 1/2] libmultipath: fallback to const prio if getprio() fails Martin Wilck
2018-03-20 16:50 ` [PATCH 2/2] multipathd: handle errors in uxlsnr as fatal Martin Wilck
2018-03-21  2:43   ` Chongyun Wu
2018-03-21  7:48     ` Martin Wilck
2018-03-22 23:31   ` Benjamin Marzinski
2018-03-20 21:13 ` Martin Wilck [this message]

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=1521580404.3798.175.camel@suse.com \
    --to=mwilck@suse.com \
    --cc=christophe.varoqui@opensvc.com \
    --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.