+++ This bug was initially created as a clone of Bug #1304966 +++
Description of problem:
DHT takes non-blocking locks while renaming files. During parallel renames and parallel rebalance and rename clients might fail with EBUSY or ESTALE errors. Hence to avoid application discontinuity renaming of files must take blocking locks.
Hence it is better to take blocking locks for renaming files.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
--- Additional comment from Vijay Bellur on 2016-02-05 04:26:34 EST ---
REVIEW: http://review.gluster.org/13366 (dht: file rename must take blocking inode locks) posted (#1) for review on master by Sakshi Bansal
Verified the bug in build - glusterfs-server-3.7.9-2.el7rhgs.x86_64.
Performed renames and lookup from different mount point on multiple dirs, no issues were seen with renames, no error messages were seen in the logs. renames completed successfully.
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.