[Bugs] [Bug 762184] Support mandatory locking in glusterfs

[bugzilla at redhat.com]

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



--- Comment #43 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/9768 committed in master by Pranith Kumar
Karampuri (pkarampu at redhat.com) 
------
commit 4517bf8dd6de310950cc5a612955aa3a2fddb57e
Author: Anoop C S <anoopcs at redhat.com>
Date:   Wed Feb 4 10:34:33 2015 +0530

    features/locks: Implement mandatory locks

    Initial change to fix/enable the mandatory locking support in GlusterFS
    as per the following design:

    https://review.gluster.org/#/c/12014/

    Accordingly 'locks.mandatory-locking' option is available as part of this
    change which will accept one among the following values:

    * off
    * file
    * forced
    * optimal

    See design doc for more details

    Change-Id: I14c489b3f8af5ebcbfa155a03f0c175e9558ac46
    BUG: 762184
    Signed-off-by: Anoop C S <anoopcs at redhat.com>
    Reviewed-on: http://review.gluster.org/9768
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Poornima G <pgurusid at redhat.com>
    Reviewed-by: Raghavendra Talur <rtalur at redhat.com>
    Reviewed-by: Rajesh Joseph <rjoseph at redhat.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=ybyuzIjDod&a=cc_unsubscribe