Bug 1226941

Summary:	nfs mount hung and gnfs server unresponsive to one of the clients
Product:	[Community] GlusterFS	Reporter:	M S Vishwanath Bhat <vbhat>
Component:	disperse	Assignee:	Pranith Kumar K <pkarampu>
Status:	CLOSED EOL	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.7.0	CC:	bugs, mzywusko, ndevos, pkarampu, skoduri, smohan
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-08 10: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 M S Vishwanath Bhat 2015-06-01 13:35:51 UTC

Description of problem:
NFS mount of in one of the clients hung and gnfs server process on the server is not responding to this particular client. It's responding to other servers. The volume is a disperse volume and had 2 bricks (redundancy count) down.

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

Built from upstream master branch with the following nightly
glusterfs-3.8dev-0.277.gitf7bc353.el6.x86_64


How reproducible:
Seen only once. Haven't tried second time.


Steps to Reproduce:
1. Run the test_disperse_basic.py tests in distaf. ( I have no other steps)

Actual results:
NFS mount hung.

Expected results:
No hang of the mountpoint.

Additional info:


I will attach the sosreports and gdb core of nfs process which was unresponsive (collected from gcore)

Comment 2 krishnan parthasarathi 2015-06-01 16:07:12 UTC

MS,
Could you provide a link or attach test script?

Comment 5 Pranith Kumar K 2015-08-04 04:09:06 UTC

http://review.gluster.org/11078 fixed the issue

Comment 7 Kaushal 2017-03-08 10:52:33 UTC

This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.