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

bugzilla at redhat.com bugzilla at redhat.com
Wed Mar 20 14:33:36 UTC 2019


            Bug ID: 1690952
           Summary: lots of "Matching lock not found for unlock xxx" when
                    using disperse (ec) xlator
           Product: GlusterFS
           Version: 5
            Status: NEW
         Component: disperse
          Assignee: bugs at gluster.org
          Reporter: kinglongmee at gmail.com
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community

This bug was initially created as a copy of Bug #1689920

I am copying this bug because: 

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:
error-xlator: test-locks [Invalid argument]

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

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

More information about the Bugs mailing list