Bug 764591 (GLUSTER-2859) - gsyncd crashes if master vol root has no xattrs
Summary: gsyncd crashes if master vol root has no xattrs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-2859
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: mainline
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ---
Assignee: Csaba Henk
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-28 15:17 UTC by Csaba Henk
Modified: 2011-05-31 17:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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)
Note You need to log in before you can comment on or make changes to this bug.