Bug 764302 (GLUSTER-2570) - getxattr failed msgs seen in log when log-level is DEBUG
Summary: getxattr failed msgs seen in log when log-level is DEBUG
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-2570
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: shishir gowda
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-21 10:37 UTC by shishir gowda
Modified: 2013-12-09 01:23 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions: master(glusterfs 3git built on Sep 14 2011)

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

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