diff options
| author | Ravishankar N <ravishankar@redhat.com> | 2015-01-23 11:12:54 +0530 |
|---|---|---|
| committer | Raghavendra Bhat <raghavendra@redhat.com> | 2015-02-03 05:24:56 -0800 |
| commit | f397d7edb85c1e4b78c4cac176dc8a0afe8cf9a8 (patch) | |
| tree | 964e187c2c8ff5e073306dd5b90f751348eafd10 /ChangeLog | |
| parent | 90f35bc8e806fc615d5e2a2657a389dbdd7e2672 (diff) | |
afr: Don't write to sparse regions of sink.
Backport of http://review.gluster.org/9480
Problem:
When data-self-heal-algorithm is set to 'full', shd just reads from
source and writes to sink. If source file happened to be sparse (VM
workloads), we end up actually writing 0s to the corresponding regions
of the sink causing it to lose its sparseness.
Fix:
If the source file is sparse, and the data read from source and sink are
both zeros for that range, skip writing that range to the sink.
Change-Id: Id23d953fe2c8c64cde5ce3530b52ef91a7583891
BUG: 1187547
Signed-off-by: Ravishankar N <ravishankar@redhat.com>
Reviewed-on: http://review.gluster.org/9515
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
Reviewed-by: Raghavendra Bhat <raghavendra@redhat.com>
Diffstat (limited to 'ChangeLog')
0 files changed, 0 insertions, 0 deletions