Bug 764302 (GLUSTER-2570)

Summary: getxattr failed msgs seen in log when log-level is DEBUG
Product: [Community] GlusterFS Reporter: shishir gowda <sgowda>
Component: coreAssignee: shishir gowda <sgowda>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: mainlineCC: gluster-bugs, nsathyan, saurabh, vijaykumar
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: master(glusterfs 3git built on Sep 14 2011) Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description shishir gowda 2011-03-21 10:37:43 UTC 
[2011-03-19 05:21:25.367897] D [compat.c:443:solaris_getxattr] 0-libglusterfs: Couldn't read extended attribute for the file 
/data/dir1/magic.mime (61)


on further investigation, the failure was seen to happen consistently for the key "gfid-req".

This key is used for setting trusted.gfid key. In lookup, the same dict is passed to posix_lookup_xattr_fill, which does a getxattr for all keys.

A check to prevent a getxattr on key gfid-req is needed.
Comment 1 Anand Avati 2011-06-14 06:38:21 UTC 
PATCH: http://patches.gluster.com/patch/6541 in master (Prevent spurious getxattr for gfid-req in posix_lookup)
Comment 2 Saurabh 2011-07-01 03:11:43 UTC 
Please update the target milestone
Comment 3 Vijaykumar 2011-09-14 04:21:41 UTC 
Its working fine. No such messages appear now.