Bug 1322532
| Summary: | [Nimble Storage] no_path_retry not working as expected with active/passive arrays when tur path checker is used. | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Ben Marzinski <bmarzins> | |
| Component: | device-mapper-multipath | Assignee: | Ben Marzinski <bmarzins> | |
| Status: | CLOSED ERRATA | QA Contact: | Lin Li <lilin> | |
| Severity: | medium | Docs Contact: | Milan Navratil <mnavrati> | |
| Priority: | unspecified | |||
| Version: | 6.7 | CC: | agk, bmarzins, dwysocha, hannsj_uhl, heinzm, lilin, msnitzer, prajnoha, prockai, rbalakri, shiva.krishna, yizhan, zkabelac | |
| Target Milestone: | rc | Keywords: | OtherQA | |
| Target Release: | 6.9 | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | device-mapper-multipath-0.4.9-94.el6 | Doc Type: | No Doc Update | |
| Doc Text: |
*device-mapper-multipath* now supports the `max_sectors_kb` configuration parameter
With this update, *device-mapper-multipath* provides a new `max_sectors_kb` parameter in the defaults, devices, and multipaths sections of the `multipath.conf` configuration file. This parameter allows you to set the 'max_sectors_kb` device queue parameter to the specified value on all underlying paths of a multipath device before the multipath device is first activated.
When a multipath device is created, the device inherits the `max_sectors_kb` value from the path devices. Manually raising this value for the multipath device or lowering this value for the path devices can cause multipath to create I/O operations larger than the path devices allow.
Using the `max_sectors_kb` `multipath.conf` parameter is an easy way to set these values before a multipath device is created on top of the path devices, and prevent invalid-sized I/O operations from being passed down.
|
Story Points: | --- | |
| Clone Of: | 1291406 | |||
| : | 1414128 (view as bug list) | Environment: | ||
| Last Closed: | 2017-03-21 10:49:51 UTC | Type: | Bug | |
| 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: | 1291406 | |||
| Bug Blocks: | 1324930, 1414128 | |||
|
Comment 3
Ben Marzinski
2016-10-15 19:15:02 UTC
hello shivamerla1, Could you help verify the bug? This bug was created as a clone of Bug #1291406. The fix is for RHEL-6.9. hello shivamerla1, Could you help test the private packages and provide feedback? This bug was created as a clone of Bug #1291406. The fix is for RHEL-6.9. thanks in advance! 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. https://rhn.redhat.com/errata/RHBA-2017-0697.html The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |