[Bugs] [Bug 1181977] gluster vol clear-locks vol-name path kind all inode return IO error in a disperse volume

[bugzilla at redhat.com]

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



--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/9444 committed in release-3.6 by Raghavendra
Bhat (raghavendra at redhat.com) 
------
commit 258f38c76f5ad816450c826becfddbe3cc91f874
Author: Xavier Hernandez <xhernandez at datalab.es>
Date:   Tue Jan 13 10:50:06 2015 +0100

    ec: Don't use inodelk on getxattr when clearing locks

    When command 'clear-locks' from cli is executed, a getxattr request
    is received by ec. This request was handled as usual, first locking
    the inode. Once this request was processed by the bricks, all locks
    were removed, including the lock used by ec.

    When ec tried to unlock the previously acquired lock (which was
    already released), caused a crash in glusterfsd.

    This fix executes the getxattr request without any lock acquired
    for the clear-locks command.

    This is a backport of http://review.gluster.org/9440/

    Change-Id: I77e550d13c4673d2468a1e13fe6e2fed20e233c6
    BUG: 1181977
    Signed-off-by: Xavier Hernandez <xhernandez at datalab.es>
    Reviewed-on: http://review.gluster.org/9444
    Reviewed-by: Dan Lambright <dlambrig at redhat.com>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Raghavendra Bhat <raghavendra 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=tKEQCr22Jc&a=cc_unsubscribe