Bug 817763

Summary: Provide a way to clear bogus locks
Product: [Community] GlusterFS Reporter: Joe Julian <joe>
Component: locksAssignee: Pranith Kumar K <pkarampu>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: mainlineCC: gluster-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-27 17:54:43 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 Joe Julian 2012-05-01 07:36:51 UTC
For the third time in two days, someone has come into the IRC channel with an invalid lock has been held on a file that needed to be self-healed. Unmounting all the clients did not clear it and the only way to clear it was to stop the volume and restart it.

It would be nice if there was a way to clear a lock that has been determined to be invalid. Maybe setting a special xattr from the client?

Comment 1 Joe Julian 2012-05-27 17:54:43 UTC

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