Bug 1701811

Summary:	ctime: Logs are flooded with "posix set mdata failed, No ctime" error during open
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Atin Mukherjee <amukherj>
Component:	core	Assignee:	Kotresh HR <khiremat>
Status:	CLOSED ERRATA	QA Contact:	Nag Pavan Chilakam <nchilaka>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.5	CC:	khiremat, nchilaka, rhs-bugs, storage-qa-internal
Target Milestone:	---
Target Release:	RHGS 3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0-2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1701457	Environment:
Last Closed:	2019-10-30 12:20:51 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:	1701457, 1702734
Bug Blocks:	1696807

Description Atin Mukherjee 2019-04-22 04:00:43 UTC

+++ This bug was initially created as a clone of Bug #1701457 +++

Description of problem:
With patch https://review.gluster.org/#/c/glusterfs/+/22540, the following log is printed many times during open

https://github.com/gluster/glusterfs/blob/1ad201a9fd6748d7ef49fb073fcfe8c6858d557d/xlators/storage/posix/src/posix-metadata.c#L625

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

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
Logs are flooded with above msg with open

Expected results:
Logs should not be flooded unless there is real issue.

Additional info:

--- Additional comment from Worker Ant on 2019-04-19 06:10:24 UTC ---

REVIEW: https://review.gluster.org/22591 (ctime: Fix log repeated logging during open) posted (#1) for review on master by Kotresh HR

Comment 8 errata-xmlrpc 2019-10-30 12:20:51 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