Bug 867342

Summary:	lookup blocked while waiting for self-heal that fails due to pre-existing locks
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Vidya Sakar <vinaraya>
Component:	glusterfs	Assignee:	Bug Updates Notification Mailing List <rhs-bugs>
Status:	CLOSED WORKSFORME	QA Contact:	Rahul Hinduja <rhinduja>
Severity:	high	Docs Contact:
Priority:	low
Version:	2.0	CC:	amarts, gluster-bugs, jdarcy, joe, pkarampu, rfortier, rhs-bugs, shaines, vagarwal, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	861308	Environment:
Last Closed:	2013-11-26 09:05:47 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:	861308
Bug Blocks:

Description Vidya Sakar 2012-10-17 10:58:00 UTC

+++ This bug was initially created as a clone of Bug #861308 +++

Description of problem:
We replaced a server and there were, apparently, stale inode locks. Directory listings, or stat to specific filenames that were affected, caused the client to hang. The only way to release those calls were to force-unmount the client.

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

How reproducible:
Always

Steps to Reproduce:
1. File with stale inode lock in with pending attributes
2. lookup() the file
  
Actual results:
Client is locked up

Expected results:
At least an error should have been returned

Additional info:

Comment 3 Amar Tumballi 2013-11-26 09:05:47 UTC

Not seen it in last year or more. Reopen if seen.