[Bugs] [Bug 1257894] "rm -rf *" from multiple mount points fails to remove directories on all the subvolumes

[bugzilla at redhat.com]

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



--- Comment #3 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13915 committed in release-3.7 by Raghavendra
G (rgowdapp at redhat.com) 
------
commit b9c37234e0933c836e1bfdb72607b592ea5080c4
Author: Sakshi <sabansal at redhat.com>
Date:   Thu Jul 16 14:31:03 2015 +0530

    dht: lock on subvols to prevent lookup vs rmdir race

    There is a possibility that while an rmdir is completed on
    some non-hashed subvol and proceeding to others, a lookup
    selfheal can recreate the same directory on those subvols
    for which the rmdir had succeeded. Now the deletion of the
    parent directory will fail with an ENOTEMPTY.

    To fix this take blocking inodelk on the subvols before
    starting rmdir. Selfheal must also take blocking inodelk
    before creating the entry.

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

    > Change-Id: I168a195c35ac1230ba7124d3b0ca157755b3df96
    > BUG: 1245065
    > Signed-off-by: Sakshi <sabansal at redhat.com>
    > Reviewed-on: http://review.gluster.org/13528
    > CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    > NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    > Smoke: Gluster Build System <jenkins at build.gluster.com>
    > Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
    > Tested-by: Raghavendra G <rgowdapp at redhat.com>

    Change-Id: I168a195c35ac1230ba7124d3b0ca157755b3df96
    BUG: 1257894
    Signed-off-by: Sakshi <sabansal at redhat.com>
    Reviewed-on: http://review.gluster.org/13915
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.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=o6wHW6yCfV&a=cc_unsubscribe