Bug 764449 (GLUSTER-2717)

Summary: Detect user_xattr mismatches for dir's
Product: [Community] GlusterFS Reporter: shishir gowda <sgowda>
Component: distributeAssignee: shishir gowda <sgowda>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: mainlineCC: gluster-bugs, lakshmipathi, nsathyan
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: RTNR Mount Type: ---
Documentation: --- CRM:
Verified Versions: master Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description shishir gowda 2011-04-12 05:05:25 UTC
The chances of user_xattr mismatching across subvols in dht is possible if the xattr gets updated/set when the brick any brick is down.

Detect this and log the key.

Comment 1 Anand Avati 2011-06-14 06:38:16 UTC
PATCH: http://patches.gluster.com/patch/6814 in master (DHT: check for mis-matching user xattrs)

Comment 2 Lakshmipathi G 2011-09-19 07:03:52 UTC
tested with master "39fee9a8f8264df61f77563acb048a441265afcf"

---
[2011-09-18 22:00:15.702925] W [dht-common.c:82:dht_aggregate] 0-dht: xattr mismatch for user.test
[2011-09-18 22:00:15.703340] W [dht-common.c:82:dht_aggregate] 0-dht: xattr mismatch for user.test
--