Description of problem: ----------------------- RHEV data domain was backed by replica 3 gluster volume and one of the node was down, while creating a image file. After self-heal, it was observed that the sparseness property on the image file on the healed NODE was no longer observed Version-Release number of selected component (if applicable): ------------------------------------------------------------- RHGS 3.1 Nightly build ( glusterfs-3.7.0-2.el6rhs ) How reproducible: ----------------- Always Steps to Reproduce: ------------------- 0. Create a 3 node trusted storage pool ( gluster cluster ) 1. Create a replica 3 volume 2. Optimize the volume for virt-store usecase 3. Start the volume 4. Use this volume as a RHEV data domain 5. Interrupt the traffic between hypervisors and one of the node in Trusted Storage Pool ( gluster cluster ) [ used iptables for this step ] 6. Create a new VM from RHEV and install RHEL 6.7 on that application VM 7. Restore the network between Hypervisor & NODE in gluster cluster 8. Initiate self-heal 9. Look for the actual size of the file on all the nodes Actual results: --------------- The VM Image file size of the node, on which the heal operation has completed has blown up to full size ( losing its sparseness ) Expected results: ----------------- VM file should continue to be a sparse file even after self-heal
This is a serious issue with VM usecase, where the expectation is to create a sparse image file,but self-heal breaks that, leading the image to occupy the full size. This would lead to admin complaining about wasted disk space. I consider this issue as a blocker for RHGS-3.1
Patch posted for review on : https://code.engineering.redhat.com/gerrit/51673 Upstream URLs: 1) master : http://review.gluster.org/11252/ 2) 3.7 : http://review.gluster.org/11423/
Verified with RHGS 3.1 Nighly build ( glusterfs-3.7.1-7.el6rhs ) with the test steps as mentioned in comment0 The size of the image file on all the nodes ( bricks ) is not increased and sparseness property of image file is retained. Marking this bug as VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1495.html