Bug 765487 (GLUSTER-3755) - setfattr -n trusted.gfid -v "SomeValue" file/directory not throwing any error
Summary: setfattr -n trusted.gfid -v "SomeValue" file/directory not throwing any error
Keywords:
Status: CLOSED UPSTREAM
Alias: GLUSTER-3755
Product: GlusterFS
Classification: Community
Component: fuse
Version: 3.2.4
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ---
Assignee: Rajesh
QA Contact: Shwetha Panduranga
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-24 09:19 UTC by Shwetha H Panduranga
Modified: 2013-07-04 22:43 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-24 11:39:54 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

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

Description Shwetha H Panduranga 2011-10-24 09:19:12 UTC 
Tested on 3.2.5qa2

[root@RHEL6 client]# setfattr -n trusted.gfid -v "New GFID Value" Testing
[root@RHEL6 client]# echo $?
0
[root@RHEL6 client]# getfattr -n trusted.gfid Testing
Testing: trusted.gfid: No such attribute

It is giving error when we are getting the trusted.gfid but not throwing any error during the "setfattr"

In the back-end there is no value set (working fine).
Comment 1 Anand Avati 2011-12-28 11:17:25 UTC 
CHANGE: http://review.gluster.com/747 (rebalance: remove the *.fix.layout xattr from trusted domain.) merged in master by Vijay Bellur (vijay)
Comment 2 Anand Avati 2012-01-14 12:58:06 UTC 
CHANGE: http://review.gluster.com/685 (core/setxattr: prevent users from setting glusterfs xattrs) merged in master by Anand Avati (avati)
Note You need to log in before you can comment on or make changes to this bug.