dm-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH 16/18] multipath-tools: Use ALUA for HP 3PAR
Date: Sun, 31 Jul 2016 01:39:23 +0200	[thread overview]
Message-ID: <aeee838a-6d44-ee76-62c5-4d97cbcaca80@gmail.com> (raw)
In-Reply-To: <trinity-e6c25fb4-7664-4f5d-9885-5aba45504689-1469916891284@3capp-gmx-bs13>

On 07/31/2016 12:14 AM, Sebastian Herbszt wrote:

> Xose Vazquez Perez wrote:

>> Sebastian was not convinced with this change, full thread: https://marc.info/?t=146175638600002
>> But there is no automatic way to change .pgpolicy from MULTIBUS to GROUP_BY_PRIO.
>> So we should stick to latest manufacturer's recommendations:

> So 'retain_attached_hw_handler' suggested by Hannes doesn't work?

No. It's related to hardware_handler, "alua" in this case.

  reply	other threads:[~2016-07-30 23:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-30  0:28 [PATCH 01/18] multipath-tools: add KOVE/XPD to hwtable Xose Vazquez Perez
2016-07-30  0:28 ` [PATCH 02/18] multipath-tools: Remove ONTAP IBM Nseries from hwtable Xose Vazquez Perez
2016-07-30  0:28 ` [PATCH 03/18] multipath-tools: reorganize NetApp devices Xose Vazquez Perez
2016-07-30  0:28 ` [PATCH 04/18] multipath-tools: add NetApp/SolidFir to hwtable Xose Vazquez Perez
2016-07-30  0:28 ` [PATCH 05/18] multipath-tools: add Nimble " Xose Vazquez Perez
2016-07-30  0:28 ` [PATCH 06/18] multipath-tools: add IBM/FlashSystem " Xose Vazquez Perez
2016-07-30  0:28 ` [PATCH 07/18] multipath-tools: add EMC/Celerra " Xose Vazquez Perez
2016-07-30  0:28 ` [PATCH 08/18] multipath-tools: add FUJITSU/ETERNUS 2000/4000/8000 " Xose Vazquez Perez
2016-07-31 19:39   ` Sebastian Herbszt
2016-07-30  0:28 ` [PATCH 09/18] multipath-tools: add VIOLIN/ "SAN ARRAY" and "SAN ARRAY ALUA" " Xose Vazquez Perez
2016-07-30  0:28 ` [PATCH 10/18] multipath-tools: add Nexsan E-Series and SATABeast/SATABoy " Xose Vazquez Perez
2016-07-30  0:28 ` [PATCH 11/18] multipath-tools: add Xiotech ISE 1400/2400/3400/3401 " Xose Vazquez Perez
2016-07-30  0:28 ` [PATCH 12/18] multipath-tools: put a comment in the correct place Xose Vazquez Perez
2016-07-30  0:28 ` [PATCH 13/18] multipath-tools: delete nearly all attribute of last member(NULL) in hwtable Xose Vazquez Perez
2016-07-30  0:28 ` [PATCH 14/18] multipath-tools: change path grouping policy for EUROLOGC/FC2502 Xose Vazquez Perez
2016-07-30  0:28 ` [PATCH 15/18] multipath-tools: add official name to Huawei devices Xose Vazquez Perez
2016-07-30  0:28 ` [PATCH 16/18] multipath-tools: Use ALUA for HP 3PAR Xose Vazquez Perez
2016-07-30 22:14   ` Sebastian Herbszt
2016-07-30 23:39     ` Xose Vazquez Perez [this message]
2016-07-31 19:06       ` Sebastian Herbszt
2016-07-31 20:43         ` Xose Vazquez Perez
2016-08-03  0:17           ` Sebastian Herbszt
2016-10-22 17:00             ` Xose Vazquez Perez
2016-07-30  0:28 ` [PATCH 17/18] multipath-tools: add HPE StoreVirtual P4000 family to hwtable Xose Vazquez Perez
2016-07-30  0:28 ` [PATCH 18/18] multipath-tools: add Oracle FS " Xose Vazquez Perez
2016-07-31  9:06 ` [PATCH 01/18] multipath-tools: add KOVE/XPD " Christophe Varoqui

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=aeee838a-6d44-ee76-62c5-4d97cbcaca80@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=dm-devel@redhat.com \
    --cc=herbszt@gmx.de \
    /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).