Bug 651389
Summary: | [NetApp 6.1 bug] Unable to set dev_loss_tmo to more than 600 through multipath.conf without setting fast_io_fail_tmo | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Rajashekhar M A <rajashekhar.a> | |
Component: | device-mapper-multipath | Assignee: | Ben Marzinski <bmarzins> | |
Status: | CLOSED ERRATA | QA Contact: | Storage QE <storage-qe> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 6.0 | CC: | agk, bdonahue, bmarzins, christophe.varoqui, coughlan, cward, dwysocha, egoggin, heinzm, junichi.nomura, kueda, lmb, mbroz, mgoodwin, prockai, tranlan, xdl-redhat-bugzilla | |
Target Milestone: | rc | Keywords: | OtherQA | |
Target Release: | 6.1 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | device-mapper-multipath-0.4.9-32.el6 | Doc Type: | Bug Fix | |
Doc Text: |
Previously, if you set dev_loss_tmo to a value greater than 600 in multipath.conf without setting the fast_io_fail_tmo value, the multipathd daemon failed to apply the setting. With this update, the multipathd daemon sets dev_loss_tmo for values over 600 correctly, as long as fast_io_fail_tmo is also set in the /etc/multipath.conf file.
|
Story Points: | --- | |
Clone Of: | ||||
: | 705854 (view as bug list) | Environment: | ||
Last Closed: | 2011-05-19 14:12:34 UTC | Type: | --- | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 705854 |
Description
Rajashekhar M A
2010-11-09 13:34:35 UTC
multipath will now set dev_loss_tmo for values over 600 correctly, as long as fast_io_fail_tmo is also set in /etc/multipath.conf ~~ Partners and Customers ~~ This bug was included in RHEL 6.1 Beta. Please confirm the status of this request as soon as possible. If you're having problems accessing 6.1 bits, are delayed in your test execution or find in testing that the request was not addressed adequately, please let us know. Thanks! 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: Previously, if you set dev_loss_tmo to a value greater than 600 in multipath.conf without setting the fast_io_fail_tmo value, the multipathd daemon failed to apply the setting. With this update, the multipathd daemon sets dev_loss_tmo for values over 600 correctly, as long as fast_io_fail_tmo is also set in the /etc/multipath.conf file. Verified this with RC1. Setting dev_loss_tmo to more than 600 now works fine if fast_io_fail_tmo is also set in /etc/multipath.conf. But if we don't set fast_io_fail_tmo in multipath.conf, the dev_loss_tmo gets configured silently with the default value (I think it's 30) without the user being warned or notified. Can multipathd throw a warning so that the user does not get confused? 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-0725.html *** Bug 816790 has been marked as a duplicate of this bug. *** |