On Wed, 2007-08-01 at 10:59 -0700, malahal@xxxxxxxxxx wrote:
> Stefan Bader [Stefan.Bader@xxxxxxxxxx] wrote:
> > I have no access to HSGs but maybe this generic statements (plus some
> > wisdom from hwtable.c) helps:
> >
> > First, you are actually forcing multipath-tools to use all paths by
> > stating "multibus" in you multipath section.
> > Everything you put there will replace the defaults and the device
> > sections. Just be minimalistic there. In the
>
> One would expect that whatever is specified in the 'device' section would
> be taken for that device no matter what is in the 'defaults' section. If
> device section is missing, then it should use from the 'defaults'
> section. Why is it implemented to have the 'defaults' section override the
> 'device' section? Looks odd to me.
You are right, Malahal. Defaults section does not override the device
section. It just overrides internal default (hwtable.c).
To my understanding the order of attribute override is as under:
internal default (hwtable.c)
defaults section (in /etc/multipath.conf)
device section (in /etc/multipath.conf)
multipaths section (in /etc/multipath.conf)
There were two things in Eric's multipath.conf which caused his problems
- setting multibus as the path grouping policy (in multipaths section)
for a device that is active/passive (it should be ideally
group_by_prio, but group_by_serial also works).
- using /bin/true as prio_callout. As Stefan pointed prio_callout
should be an appropriate one for the device.
> Thanks, Malahal.
>
> --
> dm-devel mailing list
> dm-devel@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/dm-devel
--
----------------------------------------------------------------------
Chandra Seetharaman | Be careful what you choose....
- sekharan@xxxxxxxxxx | .......you may get it.
----------------------------------------------------------------------
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
