[Bugs] [Bug 1782134] New: lots of "Matching lock not found for unlock xxx" when using disperse (ec) xlator

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1782134

            Bug ID: 1782134
           Summary: lots of "Matching lock not found for unlock xxx" when
                    using disperse (ec) xlator
           Product: GlusterFS
           Version: 7
            Status: NEW
         Component: disperse
          Severity: high
          Priority: high
          Assignee: bugs at gluster.org
          Reporter: aspandey at redhat.com
                CC: atumball at redhat.com, bkunal at redhat.com,
                    bugs at gluster.org, kinglongmee at gmail.com
        Depends On: 1689920
  Target Milestone: ---
    Classification: Community



+++ 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?


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1689920
[Bug 1689920] lots of "Matching lock not found for unlock xxx" when using
disperse (ec) xlator
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.