Don't see this in release notes, but there are a couple bugzilla's to which I 
do not have access.

Under RHEL 5.3/device-mapper-multipath-0.4.7-23.el5_3.4, these defaults:

defaults {
        path_grouping_policy group_by_prio
        rr_weight priorities
        prio_callout    "/sbin/mpath_prio_compellent /sys/block/%n/device"
}

Create groupings like this:

gilead (36000d3100008f20000000000000001d1) dm-16 COMPELNT,Compellent Vol
[size=32G][features=1 queue_if_no_path][hwhandler=0][rw]
\_ round-robin 0 [prio=100][enabled]
 \_ 2:0:1:20 sdaq 66:160  [active][ready]
 \_ 1:0:1:20 sdw  65:96   [active][ready]
\_ round-robin 0 [prio=20][enabled]
 \_ 4:0:0:20 sdew 129:128 [active][ready]
 \_ 3:0:0:20 sdex 129:144 [active][ready]

Under RHEL 5.4/device-mapper-multipath-0.4.7-30.el5, the defaults { 
path_grouping_policy } is ignored. Instead, I get multibus, verified with 
multipath -v3.

Creating a new stanza devices { device { vendor "COMPELNT"\n 
path_grouping_policy group_by_prio } } } works, but I don't know if this change 
is intentional.

Unrelatedly, kernel-xen now breaks with previously working 82575GB quad GigE 
cards. https://bugzilla.redhat.com/show_bug.cgi?id=521143
-- 
Rich Graves http://claimid.com/rcgraves
Carleton.edu Sr UNIX and Security Admin
CMC135: 507-222-7079 Cell: 952-292-6529

_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list

Reply via email to