+++ This bug was initially created as a clone of Bug #1499641 +++
Description of problem:
Glusterfs server differentiates locks based on both client-id and lock owner. There is no provision to set lk_owner as of now via gfapi. Hence a new API is needed to set the same. Since the lk_owner is associated with a particular glfd (until we get mandatory lk support), the API definition looks like below -
Version-Release number of selected component (if applicable):
Steps to Reproduce:
--- Additional comment from Soumya Koduri on 2017-10-09 03:34:27 EDT ---
--- Additional comment from Worker Ant on 2017-10-09 06:06:12 EDT ---
REVIEW: https://review.gluster.org/18429 (gfapi: set lkowner in glfd) posted (#3) for review on master by soumya k (firstname.lastname@example.org)
--- Additional comment from Worker Ant on 2017-10-10 07:57:54 EDT ---
REVIEW: https://review.gluster.org/18429 (gfapi: set lkowner in glfd) posted (#4) for review on master by soumya k (email@example.com)
Patch posted upstream for review https://review.gluster.org/18429
additional fix in nfs-ganesha-2.5.5-6
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.