Bug 1686272

Summary:	fuse mount logs inundated with [dict.c:471:dict_get] (-->/usr/lib64/glusterfs/3.12.2/xlator/cluster/replicate.so(+0x6228d) [0x7f9029d8628d] -->/usr/lib64/glusterfs/3.12.2/xlator/cluster/distribute.so(+0x202f7) [0x7f9029aa12f7] -->/lib64/libglusterfs.so.0(
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Nag Pavan Chilakam <nchilaka>
Component:	distribute	Assignee:	Nithya Balachandran <nbalacha>
Status:	CLOSED ERRATA	QA Contact:	Sayalee <saraut>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.4	CC:	mchangir, nbalacha, nchilaka, rallan, rhs-bugs, sankarshan, sheggodu, smali, storage-qa-internal
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.4.z Batch Update 4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.12.2-47	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-27 03:43:40 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:	1676400, 1695403
Bug Blocks:

Description Nag Pavan Chilakam 2019-03-07 07:11:00 UTC

Description of problem:
=======================
on my non-functional setup, I see many clients flooded with "fuse mount logs inundated with [dict.c:471:dict_get] (-->/usr/lib64/glusterfs/3.12.2/xlator/cluster/replicate.so(+0x6228d) [0x7f9029d8628d] -->/usr/lib64/glusterfs/3.12.2/xlator/cluster/distribute.so(+0x202f7) [0x7f9029aa12f7] -->/lib64/libglusterfs.so.0( "

I see that the above is being logged every few seconds

I also see there was a bug on the same issue reported in BZ#1575895 - DHT Log flooding in mount log "key=trusted.glusterfs.dht.mds [Invalid argument]"

That bug was fixed, so if they are the same then it seems to have regressed in one of the batch releases , possibly

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

How reproducible:
==============
on a handful of clients

steps:
=====
refer https://docs.google.com/spreadsheets/d/17Yf9ZRWnWOpbRyFQ2ZYxAAlp9I_yarzKZdjN8idBJM0/edit#gid=1472913705 for the steps on my non-functional testing

However, seems like a linux untar should get this problem reproduced

Comment 16 errata-xmlrpc 2019-03-27 03:43:40 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-2019:0658

Comment 17 Nithya Balachandran 2019-03-29 08:17:36 UTC

*** Bug 1678547 has been marked as a duplicate of this bug. ***