+++ This bug was initially created as a clone of Bug #1580529 +++ Description of problem: When ctime feature is enabled, access time of file which has hardlink is not changed with the cmd 'touch -a <file>' Version-Release number of selected component (if applicable): mainline How reproducible: Alwasy Steps to Reproduce: 1. Creatt gluster volume 2. Enable ctime feature (Both ctime and utime option) 3. Create a file 4. Create a hardlink for above file 5. Record atime by doing stat file 6. touch -a file 7. Record atime and compare with above. Actual results: atime should is not updated Expected results: atime should be updated Additional info: --- Additional comment from Worker Ant on 2018-05-21 13:25:41 EDT --- REVIEW: https://review.gluster.org/20051 (posix/ctime: Fix atime update for hardlink) posted (#1) for review on master by Kotresh HR --- Additional comment from Worker Ant on 2018-05-24 02:07:01 EDT --- COMMIT: https://review.gluster.org/20051 committed in master by "Kotresh HR" <khiremat> with a commit message- posix/ctime: Fix atime update for hardlink With ctime feature enabled, atime is not being updated for a hardlink when the file is accessed. e.g., touch -a <hardlink_file> fails to update atime. This patch fixes the same. fixes: bz#1580529 Change-Id: I2201c88d502d0070300a1f5023af1b36951284ec Signed-off-by: Kotresh HR <khiremat>
REVIEW: https://review.gluster.org/20078 (posix/ctime: Fix atime update for hardlink) posted (#1) for review on release-4.1 by Kotresh HR
COMMIT: https://review.gluster.org/20078 committed in release-4.1 by "Kotresh HR" <khiremat> with a commit message- posix/ctime: Fix atime update for hardlink With ctime feature enabled, atime is not being updated for a hardlink when the file is accessed. e.g., touch -a <hardlink_file> fails to update atime. This patch fixes the same. Backport of: > Patch: https://review.gluster.org/20051 > BUG: 1580529 > Change-Id: I2201c88d502d0070300a1f5023af1b36951284ec > Signed-off-by: Kotresh HR <khiremat> fixes: bz#1582072 Change-Id: I2201c88d502d0070300a1f5023af1b36951284ec Signed-off-by: Kotresh HR <khiremat>
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-v4.1.0, please open a new bug report. glusterfs-v4.1.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] http://lists.gluster.org/pipermail/announce/2018-June/000102.html [2] https://www.gluster.org/pipermail/gluster-users/