Hi,
I have now tried on a test fs, to see if I could recreate. First a bit
more info.
OS: CentOS 6.8
Gluster: 3.7.13 using centos-release-gluster37
Underlying FS (1st report): ZFS 0.6.5.7
Underlying FS (test): EXT4
# gluster vol info test
Volume Name: test
Type: Distribute
Volume ID: 291cab24-269a-4f99-a8f3-81e2c7ad6dd7
Status: Started
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: scistor01.science:/gluster/brick
Options Reconfigured:
performance.readdir-ahead: on
Procedure to recreate:
server: gluster vol create test <brick1>
server: gluster vol start test
client: (mount in /mnt/test)
client: mkdir foo
client: (check foo mtime)
server: gluster vol add-brick test <brick2>
client: (foo mtime 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)
So removing the brick again give us the right mtime again. Also,
doing this with one or two servers does not matter.
Cheers,
Hans Henrik
On 22-08-2016 15:47, Hans Henrik Happe wrote:
Hi,
We see a lot of directories that got their c+mtime updated after we
added bricks and ran a rebalance fix-layout.
On the new bricks the dirs have the current time from when fix-layout
ran. On the old they seem to be as they are supposed to. On clients some
dirs are showing the new time.
Is this a known issue and is there anything we can do about it.
Version: 3.7.13
Cheers,
Hans Henrik Happe
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
