Bug 1339197

Summary:	fuse Clients are hung on ls and find and oom kills and traces found in dmesg
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Nag Pavan Chilakam <nchilaka>
Component:	core	Assignee:	Bug Updates Notification Mailing List <rhs-bugs>
Status:	CLOSED DEFERRED	QA Contact:	Anoop <annair>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	amukherj, codonell, nbalacha, nchilaka, ravishankar, rcyriac, rhs-bugs
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-30 07:52:33 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 Nag Pavan Chilakam 2016-05-24 11:21:45 UTC

Description of problem:
=======================
I am doing stress testing for 3.1.3
Hence I populated data for 2-3 days and from 4 different clients
then after 3 days when i filled about 1TB of the 2TB volume,
I issued ls -lrt from two clients and find * from two other clients

the find * was hung on both the clients while ls -lrt was hung on one client for ever.

What I am doing can be found in http://etherpad.corp.redhat.com/3.1.3-systemic-testing
(refer line 120 and above for the intercepts)

However I found oom kills and traces in dmesg on all clients


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



Sosreports will be attached

Comment 8 Nithya Balachandran 2016-09-27 11:27:02 UTC

Based on comment#6, can we close this BZ and continue tracking any memleaks with 1379324?

Comment 9 Nithya Balachandran 2016-09-30 07:52:33 UTC

I spoke to Nag on this and he agreed that we can close this BZ and use BZ#1379324 to track this issue going forward.

Comment 10 Nag Pavan Chilakam 2017-05-02 10:11:23 UTC

removing needinfo based on comment#8 and 9