Bug 1656498
| Summary: | lvm io_setup failing due to exhausted aio contexts [rhel-7.6.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | RAD team bot copy to z-stream <autobot-eus-copy> |
| Component: | lvm2 | Assignee: | LVM and device-mapper development team <lvm-team> |
| lvm2 sub component: | Other | QA Contact: | cluster-qe <cluster-qe> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | urgent | ||
| Priority: | urgent | CC: | agk, alex.wang, bubrown, cmarthal, davem, fgarciad, heinzm, jbowen, jbrassow, jmagrini, jpittman, jualvare, lvm-team, mcsontos, mjuricek, msnitzer, mtowey, prajnoha, prockai, rhandlin, teigland, zkabelac |
| Version: | 7.6 | Keywords: | ZStream |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | lvm2-2.02.180-10.el7_6.3 | Doc Type: | If docs needed, set a value |
| Doc Text: |
Previously, if there were no aio contexts available on the system, the lvm utility failed to set up aio and terminated unexpectedly with the "io_setup failed" error message. With this update, lvm now falls back to using sync I/O when io_setup fails. As a result, the described problem no longer occurs.
|
Story Points: | --- |
| Clone Of: | 1650652 | Environment: | |
| Last Closed: | 2019-01-29 17:24:26 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: | 1650652 | ||
| Bug Blocks: | |||
|
Description
RAD team bot copy to z-stream
2018-12-05 16:13:52 UTC
I'd suggest something closer to the following (it will usually be something else on the system (not lvm) that has exhausted all available aio.) Previously, if there were no aio contexts available on the system, lvm would fail to set up aio and would terminate with the "io_setup failed" error message. With this update, lvm now falls back to using sync I/O when io_setup fails. As a result, the described problem no longer occurs. (In reply to David Teigland from comment #5) > I'd suggest something closer to the following (it will usually be something > else on the system (not lvm) that has exhausted all available aio.) > > Previously, if there were no aio contexts available on the system, lvm would > fail to set up aio and would terminate with the "io_setup failed" error > message. With this update, lvm now falls back to using sync I/O when > io_setup fails. As a result, the described problem no longer occurs. Fixed, thanks! 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://access.redhat.com/errata/RHBA-2019:0187 |