Bug 1519740

Summary:	[GSS]ganesha-gfapi log is filling at rate of 1gb/hr
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Abhishek Kumar <abhishku>
Component:	bitrot	Assignee:	Ravishankar N <ravishankar>
Status:	CLOSED ERRATA	QA Contact:	Sweta Anandpara <sanandpa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.3	CC:	abhishku, amukherj, jthottan, khiremat, ravishankar, rhinduja, rhs-bugs, srmukher, storage-qa-internal
Target Milestone:	---
Target Release:	RHGS 3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.12.2-2	Doc Type:	Bug Fix
Doc Text:	Previously, the BitRot version internal extended attribute was passed up to AFR making it launch spurious metadata self-heals on the files. With this fix, the attribute is filtered out by bit-rot preventing these heals and the corresponding messages in the log files.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-04 06:39:49 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:
Bug Depends On:
Bug Blocks:	1503138

Description Abhishek Kumar 2017-12-01 10:57:33 UTC

Description of problem:

Due to continuous metadata self-heal messages, ganesha-gfapi log is filling at rate of 1gb/hr

Version-Release number of selected component (if applicable):

RHGS 3.3

How reproducible:

Cus Environment 


Additional info:

Volume heal info doesn't any pending heals

Comment 23 Ravishankar N 2018-08-27 09:18:16 UTC

Looks good to me Srikita.

Comment 24 Ravishankar N 2018-08-27 09:19:12 UTC

(In reply to Ravishankar N from comment #23)
> Looks good to me Srikita.

Sorry for the typo Srijita.

Comment 26 errata-xmlrpc 2018-09-04 06:39:49 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/RHSA-2018:2607