Bug 1210193

Summary:	Commands hanging on the client post recovery of failed bricks
Product:	[Community] GlusterFS	Reporter:	Anoop <annair>
Component:	disperse	Assignee:	bugs <bugs>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	amukherj, annair, bugs, gluster-bugs, pkarampu, skoduri
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-05-09 17:33: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:

Description Anoop 2015-04-09 07:22:43 UTC

Description of problem:

Have following volume configuration:

Volume Name: vol1
Type: Distributed-Disperse
Volume ID: 44c0b7fa-62b6-4704-9819-57f1aac3c168
Status: Started
Number of Bricks: 2 x (4 + 2) = 12

Now, if I fail more than supported number of bricks  and recover them back, I see that the operations (like ls)from the clients hang. There is not way to get out of this state. 

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

glusterfs-3.7dev-0.885.git0d36d4f.el6.x86_64

How reproducible:

1. Create a dist. disperse
2. Mount it to a client and start I/O.
3. Failed multiple bricks and bring is back online
4. Do "ls" on the mount 


Actual results:

Mount hangs on the client

Expected results:

No hang

Additional info:

Comment 1 Soumya Koduri 2015-04-14 12:27:29 UTC

Is it always reproducible? 
Can you please post the brick/client logs. Thanks.

Comment 2 Pranith Kumar K 2015-05-09 17:33:40 UTC


*** This bug has been marked as a duplicate of bug 1205709 ***

Comment 3 Red Hat Bugzilla 2023-09-14 02:57:47 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days