Bug 1848893 - Spurious healing results in heal pending on the volume
Summary: Spurious healing results in heal pending on the volume
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: replicate
Version: rhgs-3.5
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: RHGS 3.5.z Async Update
Assignee: Ravishankar N
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1792821 1804164
TreeView+ depends on / blocked
 
Reported: 2020-06-19 07:47 UTC by Sunil Kumar Acharya
Modified: 2020-07-23 06:48 UTC (History)
13 users (show)

Fixed In Version: glusterfs-6.0-37.1
Doc Type: Bug Fix
Doc Text:
Previously, entry heal was triggered just on the source bricks even when the sink brick was down.This led to the AFR pending-xattrs on the source bricks being reset unintentionally,resulting in gfid split-brains. With this update, entry heal is triggered only when all the bricks of the replica are up, thus preventing such spurious heals leading to gfid split-brains.
Clone Of: 1804164
Environment:
rhhiv
Last Closed: 2020-07-23 06:47:39 UTC
Embargoed:
puebele: needinfo+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:3122 0 None None None 2020-07-23 06:48:04 UTC

Comment 18 SATHEESARAN 2020-07-17 11:44:38 UTC 
Verified with RHGS 3.5.2-async builds ( glusterfs-6.0-37.1 )

Validated with the following steps

1. Created the replica 3 volume
2. Used this volume as the storage domain in RHV
3. Created 10 VMs and started running kernel untar on these VMs
4. Kill of the brick and rebooted the host


When the host reboted, all the entries are healed and worked good
Comment 20 errata-xmlrpc 2020-07-23 06:47:39 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.

https://access.redhat.com/errata/RHBA-2020:3122
Note You need to log in before you can comment on or make changes to this bug.