Bug 1598926

Summary:	Misleading error messages on bricks caused by lseek
Product:	[Community] GlusterFS	Reporter:	Xavi Hernandez <jahernan>
Component:	posix	Assignee:	Xavi Hernandez <jahernan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-5.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-23 15:13:25 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:

Description Xavi Hernandez 2018-07-06 21:14:46 UTC

Description of problem:

When lseek is used with SEEK_DATA or SEEK_HOLE, an error message appears on brick logs saying that seek failed with error ENXIO (No such device or address).

This is an expected returned error when SEEK_HOLE and SEEK_DATA have reached end of file, so it shouldn't be reported as an error.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2018-07-06 21:29:33 UTC

REVIEW: https://review.gluster.org/20475 (posix: Do not log ENXIO errors for seek fop) posted (#1) for review on master by Xavi Hernandez

Comment 2 Worker Ant 2018-07-10 04:10:10 UTC

COMMIT: https://review.gluster.org/20475 committed in master by "Amar Tumballi" <amarts> with a commit message- posix: Do not log ENXIO errors for seek fop

When lseek is used with SEEK_DATA and SEEK_HOLE, it's expected that the
last operation fails with ENXIO when offset is beyond the end of file.
In this case it doesn't make sense to report this as an error log message.

This patch reports ENXIO failure messages for seek fops in debug level
instead of error level.

Change-Id: I62a4f61f99b0e4d7ea6a2cdcd40afe15072794ac
fixes: bz#1598926
Signed-off-by: Xavi Hernandez <xhernandez>

Comment 3 Shyamsundar 2018-10-23 15:13:25 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.0, please open a new bug report.

glusterfs-5.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/