Bug 1137017
| Summary: | multipath: make fast_io_fail work for iscsi devices | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Kurik <jkurik> |
| Component: | device-mapper-multipath | Assignee: | Ben Marzinski <bmarzins> |
| Status: | CLOSED ERRATA | QA Contact: | yanfu,wang <yanwang> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.5 | CC: | aberezin, agk, bazulay, bdonahue, bmarzins, ccui, cshao, dfediuck, dwysocha, fdeutsch, gouyang, hadong, heinzm, huiwa, iheim, janfrode, jboggs, jhunsaker, jkt, jmagrini, leiwang, lpeer, mkalinin, msnitzer, nsoffer, ovirt-maint, pisharma, pm-eus, prajnoha, prockai, rbalakri, rhodain, scohen, slevine, yaniwang, yanwang, ycui, yeylon, zkabelac |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | device-mapper-multipath-0.4.9-72.el6_5.4 | Doc Type: | Enhancement |
| Doc Text: |
Feature: Add iscsi support for the fast_io_fail_tmo multipath.conf option.
Reason: To allow users to modify how quickly multipath responds to failed iscsi devices with the same configuration option as they use for Fibre Channel devices.
|
Story Points: | --- |
| Clone Of: | 1099932 | Environment: | |
| Last Closed: | 2014-09-22 08:53:36 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: | 1099932 | ||
| Bug Blocks: | |||
|
Description
Jan Kurik
2014-09-03 20:37:08 UTC
Ben, can we get an estimate when we can expect the package in rhel 6.5 and fedora 19/20? Ben - you said that this is available on rhel 7 - but in our rhel 7 machines we have device-mapper-multipath-0.4.9-66!? The .el6 and .el7 release numbering is completely separate. In reality, they shouldn't even be named -0.4.9, since neither are based on that that release tarball. They are based on specfic git commits listed in the spec file, since the upstream maintained didn't release a new tarball or bump the release number for years. So, even though they both say 0.4.9, rhel7 is based on a different and much more recent upstream version, and so the numbers are referring to completely different updates. Hopefully, I will soon have fedora working off the 0.5.0 tarball. The upstream maintainer finally did bump the release number after RHEL7 GA. Fix ported. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-1271.html |