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

Bug 1607049

Summary:	Excessive logging in posix_set_parent_ctime()
Product:	[Community] GlusterFS	Reporter:	Vijay Bellur <vbellur>
Component:	posix	Assignee:	Vijay Bellur <vbellur>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, nchilaka, tdtiedem
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:
Clones:	1629548 (view as bug list)		Environment:
Last Closed:	2018-10-23 15:14:52 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:	1629548

Description Vijay Bellur 2018-07-21 11:26:39 UTC

Description of problem:

posix_set_parent_ctime() logs an error even when consistent ctime is not enabled. This causes a flood of log messages, like:

9-bmux-posix: posix utime set mdata failed on file [Function not implemented]

11-bmux-posix: posix parent set mdata failed on file [No such file or directory]

17-bmux-posix: posix parent set mdata failed on file [File exists]

This needs to be cleaned up.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2018-07-21 11:33:48 UTC

REVIEW: https://review.gluster.org/20547 (storage/posix: Avoid log flood in posix_set_parent_ctime()) posted (#1) for review on master by Vijay Bellur

Comment 2 Worker Ant 2018-07-23 03:57:49 UTC

COMMIT: https://review.gluster.org/20547 committed in master by "Amar Tumballi" <amarts> with a commit message- storage/posix: Avoid log flood in posix_set_parent_ctime()

posix_set_parent_ctime() unconditionally logs an error if consistent
time attributes is not enabled. This log does not add any value, prints
an incorrect errno & floods the log file.

Hence nuking this log message in this patch.

Change-Id: I82a78f2f8ce5ab518f8cdf6d9086a97049712f75
fixes: bz#1607049
Signed-off-by: Vijay Bellur <vbellur>

Comment 3 Travis Tiedemann 2018-09-11 20:16:11 UTC

How soon will a patch be available for this?

Comment 4 Shyamsundar 2018-10-23 15:14:52 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/