Bug 670603

Summary: 2.2.6 Need to configure set fast_io_fail_tmo in multipath.conf to 5 seconds
Product: Red Hat Enterprise Linux 5 Reporter: Chris Pelland <cpelland>
Component: vdsm22Assignee: Dan Kenigsberg <dkenigsb>
Status: CLOSED ERRATA QA Contact: yeylon <yeylon>
Severity: medium Docs Contact:
Priority: urgent    
Version: 5.6CC: abaron, apevec, bazulay, bmarzins, cpelland, danken, djorm, dpaikov, ewarszaw, hateya, iheim, mburns, mhusnain, ovirt-maint, pm-eus, Rhev-m-bugs, sgordon, srevivo, yeylon, ykaul
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: vdsm22-4.5-63.10 Doc Type: Bug Fix
Doc Text:
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 * no_path_retry fail * flush_on_last_del yes Path failover now behaves as expected.
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-10 09:18:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 658549, 672575    
Bug Blocks:    

Description Chris Pelland 2011-01-18 19:12:25 UTC
This bug has been copied from bug #658549 and has been proposed
to be backported to 5.6 z-stream (EUS).

Comment 4 Daniel Paikov 2011-01-24 12:09:25 UTC
Isn't updated in /etc/multipath.conf on vdsm22-4.5-63.13. Moving back to Assigned.

Comment 5 Dan Kenigsberg 2011-01-25 16:14:13 UTC
vdsm22-4.5-63.13.el5_6 with a fix for this was build by me only today. Please recheck.

Comment 7 Daniel Paikov 2011-01-27 10:03:52 UTC
Checked on vdsm22-4.5-63.14.el5_6.

Comment 8 Misha H. Ali 2011-03-01 04:24:11 UTC
    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

Comment 9 Stephen Gordon 2011-03-01 04:38:39 UTC
    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.

Comment 10 David Jorm 2011-03-03 03:29:53 UTC
    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

Comment 11 errata-xmlrpc 2011-03-10 09:18:39 UTC
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