Bug 1276839

Summary:	Geo-replication doesn't deal properly with sparse files
Product:	[Community] GlusterFS	Reporter:	Alex Markelov <alex>
Component:	geo-replication	Assignee:	Aravinda VK <avishwan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	avishwan, bugs, mselvaga, vbellur
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1290719 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:42:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1290719

Description Alex Markelov 2015-10-31 10:42:29 UTC

Description of problem:
Without '--sparse' option tar will not properly archive sparse file
and geo-replication will result in non-sparse file on the remote end.


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


How reproducible:
Every time you have sparse files to geo-replicate the remote end will have files full size and not sparse anymore.

Steps to Reproduce:
1. Copy a sparse file into a volume.
2. Wait for geo-replication to copy it to remote cluster.
3. Check the files on the remote end. It's no longer sparse.

Actual results:
Sparse files are no longer sparse after being geo-replicated.

Expected results:
Sparse files must remain sparse after being geo-replicated.

Additional info:
Here is more on how I arrived at this http://markelov.org/wiki/index.php/GlusterFS_3.6.1_on_CentOS_6.5:_geo-replication_and_sparse_files_problem

Comment 1 Vijay Bellur 2015-10-31 10:59:04 UTC

REVIEW: http://review.gluster.org/12476 (Add support for sparse files to tarssh method) posted (#1) for review on master by Alex Markelov (alex)

Comment 2 Vijay Bellur 2015-11-01 14:11:42 UTC

REVIEW: http://review.gluster.org/12476 (Add support for sparse files to tarssh method) posted (#2) for review on master by Venky Shankar (vshankar)

Comment 3 Vijay Bellur 2015-11-01 14:50:40 UTC

REVIEW: http://review.gluster.org/12476 (Add support for sparse files to tarssh method) posted (#3) for review on master by Vijay Bellur (vbellur)

Comment 4 Alex Markelov 2015-11-21 10:19:47 UTC

Guys, any progress with this? What about the patch that I submitted?

Comment 5 Vijay Bellur 2015-12-02 06:42:39 UTC

REVIEW: http://review.gluster.org/12476 (Add support for sparse files to tarssh method) posted (#4) for review on master by Aravinda VK (avishwan)

Comment 6 Vijay Bellur 2015-12-02 15:47:33 UTC

REVIEW: http://review.gluster.org/12476 (Add support for sparse files to tarssh method) posted (#5) for review on master by Vijay Bellur (vbellur)

Comment 7 Vijay Bellur 2015-12-10 10:01:12 UTC

REVIEW: http://review.gluster.org/12476 (Add support for sparse files to tarssh method) posted (#6) for review on master by Aravinda VK (avishwan)

Comment 8 Vijay Bellur 2015-12-11 08:27:58 UTC

COMMIT: http://review.gluster.org/12476 committed in master by Venky Shankar (vshankar) 
------
commit eff14863fb6a6da0ccf8a40343160b09f29ea493
Author: Alex Markelov <alex>
Date:   Sat Oct 31 08:30:08 2015 +0000

    Add support for sparse files to tarssh method
    
    Without '--sparse' option tar will not properly archive sparse file
    and geo-replication will result in non-sparse file on the remote end.
    
    Here is more on how I arrived at this
    http://markelov.org/wiki/index.php/GlusterFS_3.6.1_on_CentOS_6.5:_geo-replication_and_sparse_files_problem
    
    Change-Id: I8d671964a1b48bbb916e4a064571221bf3631494
    BUG: 1276839
    Signed-off-by: Alex Markelov <alex>
    Reviewed-on: http://review.gluster.org/12476
    Tested-by: Gluster Build System <jenkins.com>
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Aravinda VK <avishwan>

Comment 9 Niels de Vos 2016-06-16 13:42:20 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.

glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user