On Mon, Oct 31, 2005 at 10:51:38AM -0500, Brian Long wrote: > On Mon, 2005-10-31 at 15:07 +0100, Christophe Varoqui wrote: > > > > > > No one has automatic failback working on Clarrion storage? > > > > > Do you reproduce with upstream ? > > No. I imagine we will log a support request with Red Hat to get it > working on RHEL 4 U2. If they want to give us an updated device-mapper- > multipath RPM to try to reproduce with upstream, that's up to them. > Phil and I were just wondering if there is a specific configuration > parameter to get the trespass to happen again once all paths are back > online. > Every check interval, the daemon re-evaluates path priorities (through external prioritizers), then re-compute path-groups priorities. If PG priority order change, the highest-prio PG might be activated : - immediatly, if "failback" is set to immediate - never, if "failback" is set to manual - in a number of prio-order stable consecutive checks, if failback set to # Thus, failback/no-failback is a property of the external prioritizer, plus a framework policy switch in the name of the "failback" config file keyword. Well, at least it is the current design upstream. You'll have to dig the changelog to see if RedHat packages all the necassary bits. Regards, cvaroqui -- dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
