When I do file operations with compound fops enabled, I see lot of brick error messsages as below:
[2016-11-23 12:51:37.918491] E [inodelk.c:304:__inode_unlock_lock] 0-cfops-locks: Matching lock not found for unlock 0-9223372036854775807, by 6c10e675c57f0000 on 0x7faf7000cb30
[2016-11-23 12:51:37.918537] E [MSGID: 136002] [decompounder.c:370:dc_finodelk_cbk] 0-cfops-decompounder: fop number 2 failed. Unwinding. [Invalid argument]
[2016-11-23 12:51:37.918593] E [MSGID: 115090] [server-rpc-fops.c:2087:server_compound_cbk] 0-cfops-server: 526497: COMPOUND2 (0ea50530-9adc-424b-beb0-95f52027b671) ==> (Invalid argument) [Invalid argument]
steps to reproduce
1)create a 1x2 vol
2)fuse mount on two different fuse clients
3)untar kernel images into two different directories (one from each client)
4)while untar is happening just bring down one brick
5)check the brick log messsages
bring back the brick online
check brick logs
we can see these errors continuosly
Patch https://code.engineering.redhat.com/gerrit/91332 fixes this bug and is merged now. Moving this bug to MODIFIED state.
hit this while validating RFE 1360978 - [RFE]Reducing number of network round trips
(In reply to Krutika Dhananjay from comment #4)
> Patch https://code.engineering.redhat.com/gerrit/91332 fixes this bug and is
> merged now. Moving this bug to MODIFIED state.
Just wanted to clear one thing - when a brick is brought down and then brought back online (irrespective of whether compound-fops is enabled or not on the volume), the 'matching lock not found' failure log messages will be seen. And the appearance of these log messages is valid in that case.
However, if all replicas are up and still during IO these logs appear on the brick logs (which is what you observed), only then it is a bug.
I am not seeing these errors anymore on 3.8.4-8 with the same steps.
hence moving to verified
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.