From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christophe Varoqui Subject: Re: [PATCH v2] multipath: add detect_prio option to autodetect prioitizer Date: Sat, 12 Jan 2013 13:26:20 +0100 Message-ID: <1357993580.4263.5.camel@lapoo.opensvc.com> References: <20130110201358.GS19059@ether.msp.redhat.com> <50EFBC71.5080109@suse.de> Reply-To: christophe.varoqui@opensvc.com, device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <50EFBC71.5080109@suse.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: device-mapper development List-Id: dm-devel.ids On ven., 2013-01-11 at 08:17 +0100, Hannes Reinecke wrote: > On 01/10/2013 09:13 PM, Benjamin Marzinski wrote: > > This patch adds a new multipath.conf option, detect_prio. If set to yes, > > multipathd will try to determine the correct prioritizer for the device. If > > it finds one, that will be used instead of its configured prioritizer. If > > none is found, the configured prioritizer will be used. It can currently > > only detect ALUA devices. > > > > Also fixed and issue with select_prio where in the devices section, it was > > passing in the prio name string instead of the prio args string to prio_get() > > > > Signed-off-by: Benjamin Marzinski > > Good idea. > Don"t you think it would be fair to fallback to autodetection if no prioritizer is set, instead ? Admins would expect the values they care to set in the config file are honored. Best regards, Christophe Varoqui www.opensvc.com