[Bug 1641124] Re: Default failback value is badly chosen

Nish Aravamudan nish.aravamudan at canonical.com
Thu Jun 8 15:20:02 UTC 2017

Hello and thank you for reporting this bug! Changing default values is a
scary proposition (to me), because we have to think about every possible

What are the implications of failback=immediate over failback=manual?

Also, the base configuration for multipath "works" for all cases (I
guess unless you are installing during a failover?); if you know your
setup for multipath should use a different setting, you are able to
manage that easily (as you noted) by changing the configuration file.

The concerning part from the manpage is:

Tell multipathd how to manage path group failback.
To select \fIimmediate\fR or a \fIvalue\fR, it's mandatory that the device
has support for a working prioritizer.

We do not know that every device of every Ubuntu Server instance already
using multipath-tools has a "working prioritizer", do we? I'm not sure
what that even is, but I can guess from context in multipath :)

I'm also going to unsubscribe Ubuntu Server, as right now there is not
(in my opinion) anything for the Server Team to change -- multipath
policy is fraught with danger :) Honestly, we take the default from
upstream, because it 'just works'. If you want to see that change, I
would work with the upstream community (maybe 'immediate to manual',
which uses 'immediate' if it is detected that it can be used ('working
prioritizer') or somesuch), but that's outside the scope of the package
in Ubuntu.

** Changed in: multipath-tools (Ubuntu)
   Importance: Undecided => Wishlist

You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.

  Default failback value is badly chosen

To manage notifications about this bug go to:

More information about the Ubuntu-server-bugs mailing list