[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dm-devel
Subject:    Re: [dm-devel] [PATCH 16/18] multipath-tools: Use ALUA for HP 3PAR
From:       Xose Vazquez Perez <xose.vazquez () gmail ! com>
Date:       2016-07-31 20:43:40
Message-ID: cc29c462-f1d4-f74a-5b16-1236b48b85ea () gmail ! com
[Download RAW message or body]

On 07/31/2016 09:06 PM, Sebastian Herbszt wrote:

> Xose Vazquez Perez wrote:
>>
>> No. It's related to hardware_handler, "alua" in this case.
> 
> So how does the output of 'multipath -ll' looks like for persona 1 and 2
> with and without 'retain_attached_hw_handler'?

retain_attached_hw_handler is innocuous.
The paths grouping policy is controlled by the "path_grouping_policy" keyword,
multibus vs. group_by_prio. See man page.


Persona 1 and 2 basically is the same, but:

Persona 1:	path_grouping_policy = multibus
		failback = manual
		prio = const

Persona 2:	path_grouping_policy = group_by_prio
		failback = immediate
		prio = alua				(this is irrelevant, alua-prio is autodetected)
		hardware_handler= "1 alua"		(this is irrelevant, all hardware handlers are autodetected)

With 3PAR-OS 3.1.3, or later, you should use "Persona 2"

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
[prev in list] [next in list] [prev in thread] [next in thread]