Bug 672584

Summary: 2.2.6 - remove 'fast_io_fail_tmo' and 'dev_loss_tmo' from multipath.conf as its not supported on rhel5
Product: Red Hat Enterprise Linux 5 Reporter: Haim <hateya>
Component: vdsm22Assignee: Dan Kenigsberg <dkenigsb>
Status: CLOSED WONTFIX QA Contact: Daniel Paikov <dpaikov>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.6CC: abaron, bazulay, danken, hateya, iheim, mgoldboi, yeylon
Target Milestone: rcKeywords: Tracking
Target Release: ---   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-07 14:38:06 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: 672575    
Bug Blocks:    

Description Haim 2011-01-25 16:46:06 UTC
Description of problem:

multipath (device-mapper-multipath-0.4.7-42.el5) on RHEL5 doesn't seem to support the following flags (672575): 

    fast_io_fail_tmo        
    dev_loss_tmo  

and when initiating multipath -l, i get the following error: 

mulipath.conf line 19, invalid keyword: fast_io_fail_tmo
mulipath.conf line 20, invalid keyword: dev_loss_tmo

please reconfigure multipath and remove those entries till multipath will back-port the fix.

[root@nott-vds2 ~]# cat /etc/multipath.conf
# RHEV REVISION 0.5

attached multipath.conf output from rhel5.6

defaults {
    udev_dir                /dev
    polling_interval        5
    selector                "round-robin 0"
    path_grouping_policy    multibus
    getuid_callout          "/sbin/scsi_id -g -u -s /block/%n"
    prio_callout            /bin/true
    path_checker            readsector0
    rr_min_io               100
    max_fds                 8192
    rr_weight               priorities
    failback                immediate
    no_path_retry           fail
    user_friendly_names     no
    flush_on_last_del       yes
    fast_io_fail_tmo        5
    dev_loss_tmo            30
}

Comment 1 Dan Kenigsberg 2011-01-29 19:26:05 UTC
I don't think there's anything vdsm should do right now. Once multipath provides these options as requested in bug 672575, the issue would disappear.

Unless, of course, there is some functional effect to this temporary error message, I'll use this bug as a tracker for the multipath bug.

Comment 2 Ayal Baron 2011-03-07 14:38:06 UTC
Required underlying feature is being backported so no need for this bug.