Description of problem: With ctime feature enabled, mtime is not updated when it's set to older date than the existing time. Version-Release number of selected component (if applicable): mainline How reproducible: Always Steps to Reproduce: 1. Create gluster volume 2. Enable ctime feature as follows gluster vol set <vol> ctime on gluster vol set <vol> utime on 3. Mount the volume at say /mnt 4 touch -d "@946681200" /mnt/file1 Actual results: mtime of /mnt/file1 is not updated to 946681200 Expected results: mtime of /mnt/file1 should be updated to 946681200 Additional info:
REVIEW: https://review.gluster.org/20055 (posix/ctime: Fix updating mtime older time) posted (#1) for review on master by Kotresh HR
COMMIT: https://review.gluster.org/20055 committed in master by "Amar Tumballi" <amarts> with a commit message- posix/ctime: Fix updating mtime to older time With ctime feature enabled, the mtime is not updated when it's set to time older than the existing one. Fixed the same. But the ctime is not allowed to change to older dates. fixes: bz#1581035 Change-Id: If520922df42d6ce084c8df3046c138f8367164e5 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-5.0, please open a new bug report. glusterfs-5.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/2018-October/000115.html [2] https://www.gluster.org/pipermail/gluster-users/