Documentation< Previous | Contents | Next >
Migrated from multipath-0.4.8 to multipath-0.4.9 1.1.1. Migration from 0.4.8
The priority checkers are no longer run as standalone binaries, but as shared libraries. The key value name for this feature has also slightly changed. Copy the attribute named prio_callout to prio, also modify the argument the name of the priority checker, a system path is no longer necessary. Example conversion:
device {
vendor "NEC"
product "DISK ARRAY"
prio_callout mpath_prio_alua /dev/%n prio alua
}
See Table Priority Checker Conversion [p. 76] for a complete listing
Table 5.1. Priority Checker Conversion
v0.4.8 | v0.4.9 |
prio_callout mpath_prio_emc /dev/%n | prio emc |
prio_callout mpath_prio_alua /dev/%n | prio alua |
prio_callout mpath_prio_netapp /dev/%n | prio netapp |
prio_callout mpath_prio_rdac /dev/%n | prio rdac |
prio_callout mpath_prio_hp_sw /dev/%n | prio hp_sw |
prio_callout mpath_prio_hds_modular %b | prio hds |
Since the multipath config file parser essentially parses all key/value pairs it finds and then makes use of them, it is safe for both prio_callout and prio to coexist and is recommended that the prio attribute be inserted before beginning migration. After which you can safely delete the legacy prio_calliout attribute without interrupting service.