+++ This bug was initially created as a clone of Bug #1734370 +++ +++ This bug was initially created as a clone of Bug #1572163 +++ Description of problem: atime/mtime is not restored after healing for entry self heals Version-Release number of selected component (if applicable): Build : glusterfs-3.12.2-8.el7rhgs.x86_64 How reproducible: Always Steps to Reproduce: 1) create 1 * 3 volume 2) create a 'dir' from mount 3) kill one brick 4) touch 'dir/file' 5) bring back brick after some time 6) after healing, mtime and ctime of 'dir' will be different, while it should be same. Actual results: After healing time is not same as orginal atime/ctime of the dir From N1: # ls -lrt /bricks/brick2/b0/ total 0 drwxr-xr-x. 2 root root 18 Apr 26 03:16 dir # From N2: # ls -lrt /bricks/brick2/b1 total 0 drwxr-xr-x. 2 root root 18 Apr 26 02:47 dir # Expected results: mtime/atime should be same from all the bricks.
REVIEW: https://review.gluster.org/23226 (afr: restore timestamp of parent dir during entry-heal) posted (#1) for review on release-6 by Ravishankar N
REVIEW: https://review.gluster.org/23226 (afr: restore timestamp of parent dir during entry-heal) merged (#2) on release-6 by Ravishankar N