[Bugs] [Bug 1448299] New: Mismatch in checksum of the image file after copying to a new image file

[bugzilla at redhat.com]

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

            Bug ID: 1448299
           Summary: Mismatch in checksum of the image file after copying
                    to a new image file
           Product: GlusterFS
           Version: mainline
         Component: sharding
          Severity: medium
          Assignee: kdhananj at redhat.com
          Reporter: kdhananj at redhat.com
        QA Contact: bugs at gluster.org
                CC: bugs at gluster.org, rhs-bugs at redhat.com,
                    sasundar at redhat.com, storage-qa-internal at redhat.com
            Blocks: 1447959



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

Description of problem:
-----------------------
With sharding enabled on the replica 3 volume, when an image file is copied
from the local filesystem ( say /home/vm1.img ) to the fuse mounted sharded
replica 3 volume, checksum of source file and the copied file no longer
matches.

Version-Release number of selected component (if applicable):
--------------------------------------------------------------
RHGS 3.2.0 ( glusterfs-3.8.4-18.el7rhgs )

How reproducible:
-----------------
Always

Steps to Reproduce:
--------------------
1. Enable sharding on the replica 3 volume and fuse mount the volume
2. Create a VM image file locally on the machine ( /home/vm1.img ) and install
with OS
3. Calculate the sha256sum of the image file
4. Copy the file to the fuse mounted gluster volume.
5. Calculate the checksum of the copied image file

Actual results:
---------------
sha256sum of source file and the copied file is no longer matching

Expected results:
-----------------
sha256sum of source file and the copied file should be the same


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1447959
[Bug 1447959] Mismatch in checksum of the image file after copying to a new
image file
-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.