Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

This bug has been copied from bug #1650652 and has been proposed to be backported to 7.6 z-stream (EUS).

Comment 5 David Teigland 2019-01-23 14:53:58 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.

Comment 6 Marek Suchánek 2019-01-28 00:03:29 UTC

(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!

Comment 8 errata-xmlrpc 2019-01-29 17:24:26 UTC

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