Bug 763126 (GLUSTER-1394)

Summary:	Sparse files not in sync
Product:	[Community] GlusterFS	Reporter:	christian.boeing
Component:	glusterd	Assignee:	shishir gowda <sgowda>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	3.0.5	CC:	amarts, gluster-bugs, nsathyan, vijay
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	fuse
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description christian.boeing 2010-08-18 12:43:37 UTC

Before use glusterfs in production I made some tests:
Scenario: 2 replicated nodes

1. Create a sparse file of 50g in a folder of a mountpoint created by glusterfs.
2. Connect to a loop device (losetup /dev/loop0 ...)
-> both nodes in sync, show 50g, "du -sh" the real small size ...
3. Create a PV on /dev/loop0 (pvcreate /dev/loop0)
4. Create VG ...
5. Copy LV´s of a local VG into this VG (dd for each LV)
-> both sparse files grow in sync

Problem: If one node disapears for a time during the copy and joins again during that (test: kill glusterfsd and restart on one node) the result is that the sparse files have a different size and don´t get in sync again.

Comment 1 shishir gowda 2010-11-16 09:41:26 UTC

Hi Christian,

I ran the tests that you have specified.
On the backend, the ls and md5sum match after selfheal completes.
The du -sh size differs. 
This is valid behavior of gluster handling spare files.

With regards,
Shishir