Bug 1782134

Summary: lots of "Matching lock not found for unlock xxx" when using disperse (ec) xlator
Product: [Community] GlusterFS Reporter: Ashish Pandey <aspandey>
Component: disperseAssignee: bugs <bugs>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 7CC: atumball, bkunal, bugs, kinglongmee, pasik
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1689920 Environment:
Last Closed: 2020-01-02 06:55:10 UTC Type: ---
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: 1689920, 1787305, 1849606    
Bug Blocks:    

Description Ashish Pandey 2019-12-11 09:07:45 UTC 
+++ This bug was initially created as a clone of Bug #1689920 +++

Description of problem:

When using ec, there are many messages at brick log as,
    
E [inodelk.c:514:__inode_unlock_lock] 0-test-locks:  Matching lock not found for unlock 0-9223372036854775807, lo=68e040a84b7f0000 on 0x7f208c006f78
E [MSGID: 115053] [server-rpc-fops_v2.c:280:server4_inodelk_cbk] 0-test-server: 2557439: INODELK <gfid:df4e41be-723f-4289-b7af-b4272b3e880c> (df4e41be-723f-4289-b7af-b4272b3e880c), client: CTX_ID:67d4a7f3-605a-4965-89a5-31309d62d1fa-GRAPH_ID:0-PID:1659-HOST:openfs-node2-PC_NAME:test-client-1-RECON_NO:-28, error-xlator: test-locks [Invalid argument]

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Worker Ant on 2019-03-18 12:57:44 UTC ---

REVIEW: https://review.gluster.org/22377 (cluster-syncop: avoid duplicate unlock of inodelk/entrylk) posted (#1) for review on master by Kinglong Mee

--- Additional comment from Worker Ant on 2019-03-19 09:18:59 UTC ---

REVIEW: https://review.gluster.org/22377 (cluster-syncop: avoid duplicate unlock of inodelk/entrylk) merged (#1) on master by Kinglong Mee

--- Additional comment from Worker Ant on 2019-03-20 12:42:48 UTC ---

REVIEW: https://review.gluster.org/22385 (cluster-syncop: avoid duplicate unlock of inodelk/entrylk) posted (#1) for review on release-6 by Kinglong Mee

--- Additional comment from Worker Ant on 2019-03-20 12:44:58 UTC ---

REVIEW: https://review.gluster.org/22386 (cluster-syncop: avoid duplicate unlock of inodelk/entrylk) posted (#1) for review on release-5 by Kinglong Mee

--- Additional comment from Worker Ant on 2019-03-20 14:30:44 UTC ---

REVISION POSTED: https://review.gluster.org/22385 (cluster-syncop: avoid duplicate unlock of inodelk/entrylk) posted (#2) for review on release-6 by Kinglong Mee

--- Additional comment from Worker Ant on 2019-03-20 14:35:34 UTC ---

REVISION POSTED: https://review.gluster.org/22386 (cluster-syncop: avoid duplicate unlock of inodelk/entrylk) posted (#2) for review on release-5 by Kinglong Mee

--- Additional comment from Amar Tumballi on 2019-06-25 13:21:45 UTC ---

master branch patches are accepted.

--- Additional comment from Bipin Kunal on 2019-12-10 06:27:48 UTC ---

@Amar: Can you let me know in which glusterFS release this was taken in? Version?
Comment 1 Ashish Pandey 2019-12-23 10:07:09 UTC 


I just checked and it is present in rel-6 and rel-7.

---
Ashish
Comment 2 Ashish Pandey 2020-01-02 06:55:10 UTC 
Closing this bug as the fix is already present in release 7 which I wanted to backport.