Bug 1029444 - Able to set and get "trusted.glusterfs.volume-id" extended attribute from mount point
Summary: Able to set and get "trusted.glusterfs.volume-id" extended attribute from mou...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: 2.1
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: RHGS 3.0.0
Assignee: Vijaikumar Mallikarjuna
QA Contact: spandura
URL:
Whiteboard:
Depends On:
Blocks: 1034716
TreeView+ depends on / blocked
 
Reported: 2013-11-12 12:02 UTC by spandura
Modified: 2016-05-11 22:47 UTC (History)
5 users (show)

Fixed In Version: glusterfs-3.6.0-3.0.el6rhs
Doc Type: Bug Fix
Doc Text:
Previously we are able to get/set the "trusted.glusterfs.volume-id" extended-attribute from the mount point. After the fix xattr 'trusted.glusterfs.volume-id' not show on the mount point and throws permission error when tried to set this xattr.
Clone Of:
: 1034716 (view as bug list)
Environment:
Last Closed: 2014-09-22 19:29:34 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2014:1278 0 normal SHIPPED_LIVE Red Hat Storage Server 3.0 bug fix and enhancement update 2014-09-22 23:26:55 UTC

Description spandura 2013-11-12 12:02:56 UTC
Description of problem:
========================
We are able to get the "trusted.glusterfs.volume-id" extended-attribute from the  mount point  . Also We are able to remove, set  "trusted.glusterfs.volume-id" the extended attributes to other values from mount point.  

Version-Release number of selected component (if applicable):
================================================================
glusterfs 3.4.0.35rhs built on Oct 15 2013 14:06:04

How reproducible:
================
Often

Steps to Reproduce:
=======================
1. Create a replicate volume. Start the volume. 

2. From the client machine mount the volume. 

3. Execute : "getfattr -d -e hex -m . <mount_point>"

Actual results:
=================

Mount point:
~~~~~~~~~~~~
root@rhs-client14 [Nov-07-2013- 5:52:07] >find . | xargs getfattr -d -e hex -m .
# file: .
trusted.glusterfs.volume-id=0x51f57dabe8034e3d947163febc2ed51d

root@rhs-client14 [Nov-07-2013- 5:57:04] >setfattr -x trusted.glusterfs.volume-id .
root@rhs-client14 [Nov-07-2013- 5:57:14] >echo $?
0

Bricks:
~~~~~~~~~
root@rhs-client11 [Nov-07-2013- 5:57:26] >getfattr -d -e hex -m . /rhs/bricks/b1/
getfattr: Removing leading '/' from absolute path names
# file: rhs/bricks/b1/
trusted.gfid=0x00000000000000000000000000000001
trusted.glusterfs.dht=0x000000010000000000000000ffffffff

root@rhs-client12 [Nov-07-2013- 5:57:26] >getfattr -d -e hex -m . /rhs/bricks/b1-rep1/
getfattr: Removing leading '/' from absolute path names
# file: rhs/bricks/b1-rep1/
trusted.gfid=0x00000000000000000000000000000001
trusted.glusterfs.dht=0x000000010000000000000000ffffffff


root@rhs-client13 [Nov-07-2013- 5:57:26] >getfattr -d -e hex -m . /rhs/bricks/b1-rep2/
getfattr: Removing leading '/' from absolute path names
# file: rhs/bricks/b1-rep2/
trusted.gfid=0x00000000000000000000000000000001
trusted.glusterfs.dht=0x000000010000000000000000ffffffff

Expected results:
===================
None of the trusted.glusterfs* attributes should be visible.

Comment 2 Vijaikumar Mallikarjuna 2014-05-13 09:06:18 UTC
Patch http://review.gluster.org/#/c/6361/ fixes the issue

Comment 3 Vivek Agarwal 2014-05-22 11:53:07 UTC
Merged as a part of rebase

Comment 4 spandura 2014-06-03 06:33:20 UTC
Verified the bug on the build : "glusterfs 3.6.0.11 built on May 30 2014 11:07:25" 

Bug is fixed. Moving the bug to verified state.

Comment 6 errata-xmlrpc 2014-09-22 19:29:34 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-1278.html


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