[Bugs] [Bug 1715422] New: ctime: Upgrade/Enabling ctime feature wrongly updates older files with latest {a|m|c}time

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1715422

            Bug ID: 1715422
           Summary: ctime: Upgrade/Enabling ctime feature wrongly updates
                    older files with latest {a|m|c}time
           Product: Red Hat Gluster Storage
           Version: rhgs-3.5
            Status: NEW
         Component: core
          Assignee: atumball at redhat.com
          Reporter: khiremat at redhat.com
        QA Contact: rhinduja at redhat.com
                CC: bugs at gluster.org, pasik at iki.fi, rhs-bugs at redhat.com,
                    sankarshan at redhat.com, storage-qa-internal at redhat.com
        Depends On: 1593542
  Target Milestone: ---
    Classification: Red Hat



+++ 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:


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1593542
[Bug 1593542] ctime: Upgrade/Enabling ctime feature wrongly updates older files
with latest {a|m|c}time
-- 
You are receiving this mail because:
You are on the CC list for the bug.