This bug was initially created as a copy of Bug #1761932
I am copying this bug because:
Description of problem:
with ctime feature, ctime/mtime/atime must be consistent on a file create.
However the ctime is slightly different from mtime/atime
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.create 1x3 volume , enable features.ctime, mount volume
2. touch a file say "f1"
3. do a stat of "f1"
[root@dhcp47-105 atime]# stat ctime
Size: 0 Blocks: 0 IO Block: 131072 regular empty file
Device: 26h/38d Inode: 10974573272318328388 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2019-10-15 21:27:49.739915387 +0530
Modify: 2019-10-15 21:27:49.739915387 +0530
Change: 2019-10-15 21:27:49.740912036 +0530 -----> ctime different from a/mtime
While, I don't see any implication of the above, however this was to be fixed with ctime feature.
Don't know if there could be any implication or race conditions or a minute window of causing unexpected issues.
REVIEW: https://review.gluster.org/23719 (ctime: Fix ctime inconsisteny with utimesat) posted (#1) for review on master by Kotresh HR
REVIEW: https://review.gluster.org/23719 (ctime: Fix ctime inconsisteny with utimensat) merged (#3) on master by Amar Tumballi