[Bugs] [Bug 1272986] New: [sharding+geo-rep]: On existing slave mount, reading files fails to show sharded file content

bugzilla at redhat.com bugzilla at redhat.com
Mon Oct 19 11:21:00 UTC 2015


            Bug ID: 1272986
           Summary: [sharding+geo-rep]: On existing slave mount, reading
                    files fails to show sharded file content
           Product: GlusterFS
           Version: mainline
         Component: sharding
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: rhinduja at redhat.com
        QA Contact: bugs at gluster.org
                CC: bugs at gluster.org

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


How reproducible:


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
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
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.

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

More information about the Bugs mailing list