Bug 787151 - Irregular behaviour of the sym link creation on the slave.[3.3.0qa21]
Summary: Irregular behaviour of the sym link creation on the slave.[3.3.0qa21]
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: mainline
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
Assignee: Junaid
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-02-03 10:55 UTC by Vijaykumar Koppad
Modified: 2014-08-25 00:49 UTC (History)
4 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:38:15 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Vijaykumar Koppad 2012-02-03 10:55:19 UTC
Description of problem:
1)When i create first sym link of a file on the master it won't get reflected on the slave. But when i create the second symlink of the same file or different , first symlink gets reflected on the slave and it goes on. 

2) When i try to get xattr of the first sym link in the backend of the master, it says No such file or directory. 


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


How reproducible:always

Comment 1 Csaba Henk 2012-02-03 14:27:05 UTC
We have debugged the issue with Vijaykumar. It's happening due to symlinks not getting marked:

gluster volume create my-vol
gluster volume set my-vol indexing on
mount localhost:my-vol -t glusterfs /mnt/my-vol
cd /mnt/my-vol
ln -s foo bar
getfattr -h -d -m . -e hex bar

 -- we get no output; if xtime were present we should see it shown.

So it's a marker bug, reassigning to Junaid

Comment 2 Anand Avati 2012-02-14 09:57:36 UTC
CHANGE: http://review.gluster.com/2736 (features/marker: set loc->gfid in setxattr initiated from marker.) merged in master by Vijay Bellur (vijay)


Note You need to log in before you can comment on or make changes to this bug.