Bug 1600379

Summary: Inconsistent custom xattr on backend directories after bringing back the down sub-volumes
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Prasad Desala <tdesala>
Component: distributeAssignee: Tamar Shacked <tshacked>
Status: CLOSED ERRATA QA Contact: Pranav Prakash <prprakas>
Severity: medium Docs Contact:
Priority: high    
Version: rhgs-3.4CC: csaba, moagrawa, pasik, pprakash, rhs-bugs, sheggodu, shilpsha, tshacked
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.5.z Batch Update 7   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-6.0-57 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-10-05 07:56:26 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-07-12 06:42:44 UTC 
Description of problem:
=======================
Inconsistent custom xattr on directories after bringing back the down sub-volume.

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

How reproducible:
always

Steps to Reproduce:
===================
1) Create a distributed-replicate volume and start it.
2) FUSE mount on a client.
3) From mount, create a directory "dir".
4) set custom attribute for directory "dir" and verify it on all server.
5) Bring down a sub-volume.
6) Remove the xattr set for directory "dir".
7) Bring back the down sub-volume.
8) Send a lookup from mount point.
9) Check for the xattr on the directory on the down subvols.

Actual results:
===============
Removed xattr are still seen after bringing back the down subvols. Leading to inconsistency.

Expected results:
=================
Custom xattr should be consistent across all the subvols.

Additional info:
[     OK] Disk used percentage  path=/  percentage=19
[     OK] Disk used percentage  path=/var  percentage=19
[     OK] Disk used percentage  path=/tmp  percentage=19
[     OK] All peers are in connected state  connected_count=5  total_peer_count=5
[     OK] no gfid mismatch
[ NOT OK] Failed to check op-version
[     OK] The maximum size of core files created is set to unlimted.
[  ERROR] Report failure  report=report_check_worker_restarts
[  ERROR] Report failure  report=report_non_participating_bricks
[     OK] Glusterd is running  uptime_sec=596907
[WARNING] Errors in Glusterd log file  num_errors=89
[WARNING] Warnings in Glusterd log file  num_warning=32
[     OK] No errors seen at network card
[     OK] No errors seen at network card
High CPU usage by Self-heal
[WARNING] Errors in Glusterd log file num_errors=122
[WARNING] Warnings in Glusterd log file num_warnings=51
Comment 20 errata-xmlrpc 2021-10-05 07:56:26 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 (RHGS 3.5.z Batch Update 5 glusterfs bug fix and enhancement update), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2021:3729