Bug 787656

Summary: [b708b18b833d1f2ba4da394884bc762a821ff56b]: lot of unlock failed errors afr_unlock_inodelk_cbk
Product: [Community] GlusterFS Reporter: Rahul C S <rahulcs>
Component: replicateAssignee: Pranith Kumar K <pkarampu>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: pre-releaseCC: gluster-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-07 06:19:25 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:
Attachments:
Description Flags
failing unlock logs none

Description Rahul C S 2012-02-06 12:35:06 UTC
Created attachment 559627 [details]
failing unlock logs

Description of problem:
Created a volume with the following info
Volinfo:
Volume Name: vol
Type: Distributed-Replicate
Volume ID: 7249b2f3-83fe-47bc-940d-bd30ff1e4025
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: dagobah:/data/export1
Brick2: dagobah:/data/export2
Brick3: dagobah:/data/export3
Brick4: dagobah:/data/export4
Options Reconfigured:
performance.stat-prefetch: off
cluster.data-self-heal-algorithm: diff
performance.flush-behind: off
features.limit-usage: /:8GB
diagnostics.count-fop-hits: on
diagnostics.latency-measurement: on
features.quota: on
geo-replication.indexing: on


Mounted 2 clients, one running bonnie++ & another running fileop, did a lot of healing, brick up & down.
Bonnie++ options: bonnie++ -d . -x 10 -u root -r 2MB
fileop options: fileop -f 30 -t

Client logs:
[2012-02-06 16:13:58.787840] W [client3_1-fops.c:1311:client3_1_finodelk_cbk] 3-vol-client-1: remote operation failed: Invalid argument
[2012-02-06 16:13:58.787876] E [afr-lk-common.c:568:afr_unlock_inodelk_cbk] 3-vol-replicate-0: /Bonnie.10996/0000001f4fKifn9M: unlock failed on 1, reason: Invalid argument
[2012-02-06 16:14:00.602725] W [client3_1-fops.c:1311:client3_1_finodelk_cbk] 3-vol-client-2: remote operation failed: Invalid argument
[2012-02-06 16:14:00.602767] E [afr-lk-common.c:568:afr_unlock_inodelk_cbk] 3-vol-replicate-1: /Bonnie.10996/0000001facUEt6g: unlock failed on 0, reason: Invalid argument
[2012-02-06 16:15:57.403122] W [client3_1-fops.c:1311:client3_1_finodelk_cbk] 3-vol-client-1: remote operation failed: Invalid argument
[2012-02-06 16:15:57.403200] E [afr-lk-common.c:568:afr_unlock_inodelk_cbk] 3-vol-replicate-0: /Bonnie.10996/00000029a5Lu3IEp: unlock failed on 1, reason: Invalid argument
[2012-02-06 16:15:59.474133] W [client3_1-fops.c:1311:client3_1_finodelk_cbk] 3-vol-client-1: remote operation failed: Invalid argument
[2012-02-06 16:15:59.474164] E [afr-lk-common.c:568:afr_unlock_inodelk_cbk] 3-vol-replicate-0: /Bonnie.10996/0000002a4eIgHTPxM: unlock failed on 1, reason: Invalid argument
[2012-02-06 16:16:20.793158] W [client3_1-fops.c:1311:client3_1_finodelk_cbk] 3-vol-client-1: remote operation failed: Invalid argument
[2012-02-06 16:16:20.793234] E [afr-lk-common.c:568:afr_unlock_inodelk_cbk] 3-vol-replicate-0: /Bonnie.10996/0000002bceePb: unlock failed on 1, reason: Invalid argument
[2012-02-06 16:16:33.803821] W [client3_1-fops.c:1311:client3_1_finodelk_cbk] 3-vol-client-1: remote operation failed: Invalid argument
[2012-02-06 16:16:33.931458] E [afr-lk-common.c:568:afr_unlock_inodelk_cbk] 3-vol-replicate-0: /Bonnie.10996/0000002ee6o1sxmqChi: unlock failed on 1, reason: Invalid argument
[2012-02-06 16:18:56.181615] W [client3_1-fops.c:1311:client3_1_finodelk_cbk] 3-vol-client-1: remote operation failed: Invalid argument
[2012-02-06 16:18:56.413373] E [afr-lk-common.c:568:afr_unlock_inodelk_cbk] 3-vol-replicate-0: /Bonnie.10996/0000003f5bAFgRjT: unlock failed on 1, reason: Invalid argument

Attaching logs.

Comment 1 Pranith Kumar K 2012-02-07 06:19:25 UTC
Rahul,
    Whenever there is a disconnect the server deletes all the locks on that transport. That is why when the actual unlock post the reconnect is issued, it will give this error because the lock wont be there on the server anymore.

Pranith

*** This bug has been marked as a duplicate of bug 770080 ***