Bug 1274600

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

Description of problem:
=======================

In geo-rep setup, when a data on file increases beyond 4M size the files gets synced to slave but reading file from slave mount only shows the original file content and not the content of sharded chunk. 

Unmounting and remounting the slave volume shows the proper content including sharded file contents. 

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

glusterfs-3.8dev-0.929.gitbece485.el7rhgs.x86_64


How reproducible:
=================

Always


Steps to Reproduce:
===================
1. Create Master and Slave Cluster
2. Create Master and Slave Volume with meta_volume to true and features.shard on. Also enable performance.strict-write-ordering on the master volume
3. Create and Start geo-rep session
4. Mount master and slave volume
5. Create a file with total size less than 4M {I created file_1.9M with 1.9M of size}
6. File should sync to slave. Calculate arequal between master and slave, it should match. Do a diff of file between master and slave, should not show any output.
7. Append the existing file with data to grow total size more than 4M {I appended data of 3.4M to file_1.9M, total size thus becomes 5.2M}
8. Confirm 1 sharded file is created
9. Size at master and slave for file_1.9M is correctly shown as 5.2M but the arequal missmatches. diff shows data is not synced from master to slave. Their is a miss match in sharded files.
10. Umount the slave volume
11. Mount the slave volume again. The arequal matches

Actual results:
===============

On existing slave mount, the file content may be read from some cache


Expected results:
=================

On existing volume, the file should be read as whole including the shareded file content.

--- Additional comment from Vijay Bellur on 2015-10-20 05:31:36 EDT ---

REVIEW: http://review.gluster.org/12400 (features/shard: Refresh cached size when lookup/readdirp detect that xattr value has changed) posted (#1) for review on master by Krutika Dhananjay (kdhananj)

--- Additional comment from Vijay Bellur on 2015-10-20 07:46:40 EDT ---

REVIEW: http://review.gluster.org/12400 (features/shard: Force cache-refresh when lookup/readdirp/stat detect that xattr value has changed) posted (#2) for review on master by Krutika Dhananjay (kdhananj)