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

Bug 1644129

Summary: Excessive logging in posix_update_utime_in_mdata
Product: [Community] GlusterFS Reporter: Kotresh HR <khiremat>
Component: ctimeAssignee: Kotresh HR <khiremat>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-6.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1644524 1644526 (view as bug list) Environment:
Last Closed: 2018-11-28 06:06:06 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: 1644524, 1644526    

Description Kotresh HR 2018-10-30 05:24:38 UTC 
Description of problem:
posix_update_utime_in_mdata  logs an error even when consistent ctime is not enabled. This causes a flood of log messages, like:

[2018-09-28 12:44:26.636267] W [MSGID: 113117] [posix-metadata.c:569:posix_update_utime_in_mdata] 0-dyn_cfu-posix: posix utime set mdata failed on file [Invalid argument]
[2018-09-28 12:44:31.564728] W [MSGID: 113117] [posix-metadata.c:569:posix_update_utime_in_mdata] 0-dyn_cfu-posix: posix utime set mdata failed on file
[2018-09-28 12:44:47.156757] W [MSGID: 113117] [posix-metadata.c:569:posix_update_utime_in_mdata] 0-dyn_cfu-posix: posix utime set mdata failed on file [Function not implemented]
The message "W [MSGID: 113117] [posix-metadata.c:569:posix_update_utime_in_mdata] 0-dyn_cfu-posix: posix utime set mdata failed on file [Invalid argument]" repeated 52 times 

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-10-31 05:07:38 UTC 
REVIEW: https://review.gluster.org/21520 (posix/ctime: Avoid log flood in posix_update_utime_in_mdata) posted (#1) for review on master by Kotresh HR
Comment 2 Worker Ant 2018-11-02 01:05:56 UTC 
REVIEW: https://review.gluster.org/21520 (posix/ctime: Avoid log flood in posix_update_utime_in_mdata) posted (#2) for review on master by Amar Tumballi
Comment 3 Kotresh HR 2018-11-28 06:06:06 UTC 
Fixed in v5.1
Comment 4 Shyamsundar 2019-03-25 16:31:39 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-6.0, please open a new bug report.

glusterfs-6.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/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/