+++ This bug was initially created as a clone of Bug #1593542 +++

Description of problem:
Upgrade scenario: Currently for older files, the ctime gets updated during {a|m|c}time modification fop and eventually becomes consistent. 
With any {a|m|c}time modification, the ctime is initialized with latest time which is incorrect. So how do we handle this upgrade scenario.

Version-Release number of selected component (if applicable):
mainline

How reproducible:
Always

Steps to Reproduce:
1.  Create EC/replica volume, mount it, create a file.
2.  Enable ctime feature
3.  touch the created file {m|a|c}time will be latest. Only access time should have been updated.

Actual results:
 {a|m|c}time gets updated.

Expected results:
 Only access time should have been updated.


Additional info:

--- Additional comment from Worker Ant on 2019-06-24 19:11:36 UTC ---

REVIEW: https://review.gluster.org/22936 (ctime: Set mdata xattr on legacy files) posted (#1) for review on master by Kotresh HR

--- Additional comment from Worker Ant on 2019-07-22 06:57:08 UTC ---

REVIEW: https://review.gluster.org/22936 (ctime: Set mdata xattr on legacy files) merged (#14) on master by Atin Mukherjee

--- Additional comment from Worker Ant on 2019-07-22 15:30:46 UTC ---

REVIEW: https://review.gluster.org/23091 (features/utime: Fix mem_put crash) posted (#1) for review on master by Pranith Kumar Karampuri

--- Additional comment from Worker Ant on 2019-07-23 01:29:55 UTC ---

REVIEW: https://review.gluster.org/23091 (features/utime: Fix mem_put crash) merged (#1) on master by Pranith Kumar Karampuri