Bug 867342 - lookup blocked while waiting for self-heal that fails due to pre-existing locks
Summary: lookup blocked while waiting for self-heal that fails due to pre-existing locks
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterfs
Version: 2.0
Hardware: Unspecified
OS: Unspecified
low
high
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: Rahul Hinduja
URL:
Whiteboard:
Depends On: 861308
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-17 10:58 UTC by Vidya Sakar
Modified: 2013-11-26 09:05 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 861308
Environment:
Last Closed: 2013-11-26 09:05:47 UTC
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.