Bug 1567745

Summary: dht.commithash xattr is not assigned to a newly created volume
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Prasad Desala <tdesala>
Component: distributeAssignee: Nithya Balachandran <nbalacha>
Status: CLOSED WONTFIX QA Contact: Prasad Desala <tdesala>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.4CC: nbalacha, rhs-bugs, storage-qa-internal, tdesala
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-10 03:12:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Prasad Desala 2018-04-16 07:12:01 UTC 
Description of problem:
=======================
commithash mechanism which lookup optimize uses is not assigned to a newly created volume. 
With cluster.lookup-optimize enabled default in code for 3.4.0, when a new volume is created dht.commithash xattr should be assigned to the volume.

getfattr -d -e hex -m . /bricks/brick*/commit-*/
getfattr: Removing leading '/' from absolute path names
# file: bricks/brick0/commit-b0/
security.selinux=0x73797374656d5f753a6f626a6563745f723a676c7573746572645f627269636b5f743a733000
trusted.gfid=0x00000000000000000000000000000001
trusted.glusterfs.dht=0x0000000100000000000000007ffffffe
trusted.glusterfs.volume-id=0x85e3f07e1e2244b3abafafdccbd446f9

Version-Release number of selected component (if applicable):
3.12.2-7.el7rhgs.x86_64

How reproducible:
always

Steps to Reproduce:
===================
1) On 3.12.2-7.el7rhgs.x86_64 (this build has lookup-optimize enabled by default in code), create a x3 volume.
2) FUSE mount it on a client and do a lookup.
3) Check for commithash xattr on the backend bricks.

Actual results:
===============
dht.commithash xattr is not assigned to a newly created volume.

Expected results:
=================
when a new volume is created with lookup-optimize enabled, dht.commithash xattr should be assigned to the volume.
Comment 10 Nithya Balachandran 2019-10-10 03:12:22 UTC 
As the lack of the xattr is treated as a zero commit hash value, this does not affect the functionality. Closing this with WontFix.