Bug 1689920 - lots of "Matching lock not found for unlock xxx" when using disperse (ec) xlator
Summary: lots of "Matching lock not found for unlock xxx" when using disperse (ec) xlator
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: disperse
Version: mainline
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1782134 1787305 1849606
TreeView+ depends on / blocked
 
Reported: 2019-03-18 12:54 UTC by Kinglong Mee
Modified: 2020-06-22 11:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1782134 1787305 (view as bug list)
Environment:
Last Closed: 2019-06-25 13:21:45 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 22377 0 None Open cluster-syncop: avoid duplicate unlock of inodelk/entrylk 2019-03-19 09:18:58 UTC

Description Kinglong Mee 2019-03-18 12:54:43 UTC 
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:
Comment 1 Worker Ant 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
Comment 2 Worker Ant 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
Comment 3 Worker Ant 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
Comment 4 Worker Ant 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
Comment 5 Worker Ant 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
Comment 6 Worker Ant 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
Comment 7 Amar Tumballi 2019-06-25 13:21:45 UTC 
master branch patches are accepted.
Note You need to log in before you can comment on or make changes to this bug.