Hide Forgot
This bug has been copied from bug #658549 and has been proposed to be backported to 5.6 z-stream (EUS).
Isn't updated in /etc/multipath.conf on vdsm22-4.5-63.13. Moving back to Assigned.
vdsm22-4.5-63.13.el5_6 with a fix for this was build by me only today. Please recheck.
Checked on vdsm22-4.5-63.14.el5_6.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: WIP
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1,7 @@ -WIP+In Red Hat Enterprise Linux 5.6, high default values for dev_loss_tmo, polling_intervals, and fast_io_fail_tmo, and the default values for no_path_retry and flush_on_last_del resulted in slow path failover. The default values of these parameters have been updated in the current VDSM package as follows: + * dev_loss_tmo 30 + * polling_intervals 5 + * fast_io_fail_tmo 5 + * no_path_retry fail + * flush_on_last_del yes +Path failover now behaves as expected.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,4 +1,4 @@ -In Red Hat Enterprise Linux 5.6, high default values for dev_loss_tmo, polling_intervals, and fast_io_fail_tmo, and the default values for no_path_retry and flush_on_last_del resulted in slow path failover. The default values of these parameters have been updated in the current VDSM package as follows: +The default values for the dev_loss_tmo, polling_intervals, fast_io_fail_tmo, no_path_retry and flush_on_last_del parameters resulted in slow path failover. The default values of these parameters have been updated in the current VDSM package as follows: * dev_loss_tmo 30 * polling_intervals 5 * fast_io_fail_tmo 5
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0319.html