[Bugs] [Bug 1370832] New: Directory timestamps change after add-brick

[bugzilla at redhat.com]

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

            Bug ID: 1370832
           Summary: Directory timestamps change after add-brick
           Product: GlusterFS
           Version: 3.7.13
         Component: glusterd
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: happe at nbi.dk
                CC: bugs at gluster.org



Description of problem:
After add-brick directory timestamps change to current time.

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

OS: CentOS 6.8
Gluster: 3.7.13 using centos-release-gluster37
Underlying filesystems tested: ZFS 0.6.5.7, EXT4


How reproducible:
Every time.

Steps to Reproduce:
One server is enough. Have tested with one initial brick and two initial
bricks.

server: gluster vol create test <brick1>
server: gluster vol start test
client: (mount in /mnt/test)
client: mkdir /mnt/test/foo
client: (check foo timestamps)
server: gluster vol add-brick test <brick2>
client: (if NFS re-mount is required, guess caching)
client: (foo timestamps now changed)
server: gluster vol remove-brick test <brick2> start
server: gluster vol remove-brick test <brick2> commit
client: (foo mtime now back to expected time)

Actual results:
Directory have different timestamps.
When brick is removed again, the timestamps are correct again.

Expected results:
Directory timestamps are not altered.

Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.