[Bugs] [Bug 1305836] New: DHT: Take blocking locks while renaming files

bugzilla at redhat.com bugzilla at redhat.com
Tue Feb 9 11:29:15 UTC 2016


            Bug ID: 1305836
           Summary: DHT: Take blocking locks while renaming files
           Product: Red Hat Gluster Storage
           Version: 3.1
         Component: gluster-dht
          Severity: medium
          Assignee: rhs-bugs at redhat.com
          Reporter: rhinduja at redhat.com
        QA Contact: storage-qa-internal at redhat.com
                CC: bugs at gluster.org, sabansal at redhat.com
        Depends On: 1304966

+++ 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

Hence it is better to take blocking locks for renaming files.

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

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

--- 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

Referenced Bugs:

[Bug 1304966] DHT: Take blocking locks while renaming files
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=JnlxupGDvZ&a=cc_unsubscribe

More information about the Bugs mailing list