Bug 1701811 - ctime: Logs are flooded with "posix set mdata failed, No ctime" error during open
Summary: ctime: Logs are flooded with "posix set mdata failed, No ctime" error during ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: core
Version: rhgs-3.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: RHGS 3.5.0
Assignee: Kotresh HR
QA Contact: Nag Pavan Chilakam
URL:
Whiteboard:
Depends On: 1701457 1702734
Blocks: 1696807
TreeView+ depends on / blocked
 
Reported: 2019-04-22 04:00 UTC by Atin Mukherjee
Modified: 2019-10-30 12:21 UTC (History)
4 users (show)

Fixed In Version: glusterfs-6.0-2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1701457
Environment:
Last Closed: 2019-10-30 12:20:51 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:3249 0 None None None 2019-10-30 12:21:19 UTC

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


Note You need to log in before you can comment on or make changes to this bug.