Bug 764591 (GLUSTER-2859)

Summary:	gsyncd crashes if master vol root has no xattrs
Product:	[Community] GlusterFS	Reporter:	Csaba Henk <csaba>
Component:	geo-replication	Assignee:	Csaba Henk <csaba>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	mainline	CC:	gluster-bugs, lakshmipathi
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:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Csaba Henk 2011-04-28 15:17:03 UTC

Set up a single brick volume, start it. Remove or rename it's backing directory and create an empty one in place of it.

Expected behavior: setting up geo-rep with this vol as master works.
Actual behavior: gsyncd crashes with TypeError when listing xattrs on root node.

Comment 1 Anand Avati 2011-05-09 17:27:06 UTC

PATCH: http://patches.gluster.com/patch/7097 in master (syncdaemon: fix listing xattrs when there is none and failure handling)

Comment 2 Lakshmipathi G 2011-05-31 10:42:25 UTC

tested with above patch on 3.2.0. 
created a single brick volume and started gsync from master to slave. files got synced. then renamed and created empty dir 
(#mv /export/dir /export/DIR && mkdir /export/dir)
Created few more files and dirs they are still synced to slave.

Comment 3 Anand Avati 2011-05-31 14:01:48 UTC

PATCH: http://patches.gluster.com/patch/7341 in release-3.2 (syncdaemon: fix listing xattrs when there is none and failure handling)