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:
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
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
Fixed in v5.1
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/