[Bugs] [Bug 1412922] ls and move hung on disperse volume

bugzilla at redhat.com bugzilla at redhat.com
Tue Jan 17 15:55:44 UTC 2017


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



--- Comment #3 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: http://review.gluster.org/16394 committed in release-3.8 by Pranith
Kumar Karampuri (pkarampu at redhat.com) 
------
commit d724b4213902b694ec13a48bc4d55d538986787f
Author: Pranith Kumar K <pkarampu at redhat.com>
Date:   Thu Dec 8 14:53:04 2016 +0530

    cluster/ec: Fix lk-owner set race in ec_unlock

    Problem:
    Rename does two locks. There is a case where when it tries to unlock it
sends
    xattrop of the directory with new version, callback of these two xattrops
can
    be picked up by two separate epoll threads. Both of them will try to set
the
    lk-owner for unlock in parallel on the same frame so one of these unlocks
will
    fail because the lk-owner doesn't match.

    Fix:
    Specify the lk-owner which will be set on inodelk frame which will not be
over
    written by any other thread/operation.

     >BUG: 1402710
     >Change-Id: I666ffc931440dc5253d72df666efe0ef1d73f99a
     >Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
     >Reviewed-on: http://review.gluster.org/16074
     >Reviewed-by: Xavier Hernandez <xhernandez at datalab.es>
     >Smoke: Gluster Build System <jenkins at build.gluster.org>
     >NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
     >CentOS-regression: Gluster Build System <jenkins at build.gluster.org>

    BUG: 1412922
    Change-Id: I18c553adaa0cbc8df55876accc1e1dcd4ee9c116
    Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
    Reviewed-on: http://review.gluster.org/16394
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez at datalab.es>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list