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:
REVIEW: https://review.gluster.org/22936 (ctime: Set mdata xattr on legacy files) posted (#1) for review on master by Kotresh HR
REVIEW: https://review.gluster.org/22936 (ctime: Set mdata xattr on legacy files) merged (#14) on master by Atin Mukherjee
REVIEW: https://review.gluster.org/23091 (features/utime: Fix mem_put crash) posted (#1) for review on master by Pranith Kumar Karampuri
REVIEW: https://review.gluster.org/23091 (features/utime: Fix mem_put crash) merged (#1) on master by Pranith Kumar Karampuri