Bug 1744518

Summary:	log aio_error return codes in posix_fs_health_check
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Mohit Agrawal <moagrawa>
Component:	posix	Assignee:	Mohit Agrawal <moagrawa>
Status:	CLOSED ERRATA	QA Contact:	Nag Pavan Chilakam <nchilaka>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.5	CC:	nchilaka, rhinduja, rhs-bugs, sheggodu, storage-qa-internal
Target Milestone:	---
Target Release:	RHGS 3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0-13	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1744519 (view as bug list)		Environment:
Last Closed:	2019-10-30 12:22:40 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:
Bug Blocks:	1696809, 1744519

Description Mohit Agrawal 2019-08-22 10:18:25 UTC

Description of problem:
in posix_health_check function log aio_error return code in the message while aio operation is failed. Sometime brick is going down to health check thread is 
failed without logging error codes return by aio system calls.As per aio_error man page it returns a positive error number if the asynchronous I/O operation failed.

Version-Release number of selected component (if applicable):


How reproducible:
Only reproducible in QE environment

Steps to Reproduce:
1.
2.
3.

Actual results:
health check thread is failing without logging aio return codes.

Expected results:
Log message should print error code in case of error.

Additional info:

Comment 2 Sunil Kumar Acharya 2019-08-22 11:16:19 UTC

Upstream Patch: https://review.gluster.org/23284

Comment 9 errata-xmlrpc 2019-10-30 12:22:40 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/RHEA-2019:3249