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

bugzilla at redhat.com bugzilla at redhat.com
Wed Dec 14 12:38:29 UTC 2016


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



--- Comment #3 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: http://review.gluster.org/16130 committed in release-3.9 by Pranith
Kumar Karampuri (pkarampu at redhat.com) 
------
commit e8b4e119e00f3599acb0ea95f8237cf9b07546a3
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: 1404572
    Change-Id: Iff4f0c1364e6533f3c07f192138bcd321789b4cd
    Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
    Reviewed-on: http://review.gluster.org/16130
    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>

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