[Bugs] [Bug 1339446] ENOTCONN error during parallel rmdir

bugzilla at redhat.com bugzilla at redhat.com
Wed May 25 10:37:12 UTC 2016


https://bugzilla.redhat.com/show_bug.cgi?id=1339446



--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14528 committed in release-3.7 by Pranith
Kumar Karampuri (pkarampu at redhat.com) 
------
commit 8da90277f5f80ffffaa3e9f9ccee6f90c293cc03
Author: Ravishankar N <ravishankar at redhat.com>
Date:   Wed May 18 14:37:46 2016 +0530

    cluster/afr: Check for required number of entrylks

    Backport of: http://review.gluster.org/14358

    Problem:
    Parallel rmdir operations on the same directory results in ENOTCONN
messages
    eventhough there was no network disconnect.

    In blocking entry lock during rmdir, AFR takes 2 set of locks on all its
    children-One (parentdir,name of dir to be deleted), the other (full lock
    on the dir being deleted). We proceed to pre-op stage even if only a single
    lock (but not all the needed locks) was obtained, only to fail it with
ENOTCONN
    because afr_locked_nodes_get() returns zero nodes  in
afr_changelog_pre_op().

    Fix:
    After we get replies for all blocking lock requests, if we don't have
    the minimum number of locks to carry out the FOP, unlock and fail the
    FOP. The op_errno will be that of the last failed reply we got, i.e.
    whatever is set in afr_lock_cbk().

    Change-Id: I9fcb6bec0335dd9cdd851a92cb08605b4a959e64
    BUG: 1339446
    Signed-off-by: Ravishankar N <ravishankar at redhat.com>
    Reviewed-on: http://review.gluster.org/14528
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>

-- 
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=rqCeA0mPO8&a=cc_unsubscribe


More information about the Bugs mailing list