[Bugs] [Bug 1232378] [remove-brick]: Creation of file from NFS writes to the decommissioned subvolume and subsequent lookup from fuse creates a link

[bugzilla at redhat.com]

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



--- Comment #14 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/11260 committed in master by Raghavendra G
(rgowdapp at redhat.com) 
------
commit 1626fb105c99ef623be3687f3f48d9247ab9b7c4
Author: Susant Palai <spalai at redhat.com>
Date:   Tue Jun 16 20:35:46 2015 +0530

    dht: block/handle create op falling to decommissioned brick

    Problem:
    Post remove-brick start till commit phase, the client layout
    may not be in sync with disk layout because of lack of lookup.
    Hence,a create call may fall on the decommissioned brick.

    Solution:
    Will acquire a lock on hashed subvol. So that a fix-layout or
    selfheal can not step on layout while reading the layout.

    Even if we read a layout before remove-brick fix-layout and the
    file falls on the decommissioned brick, the file should be
    migrated to a new brick as per the fix-layout.

    Change-Id: If84a12ec34f981adb2b9b224e80f535cfe5bf9f2
    BUG: 1232378
    Signed-off-by: Susant Palai <spalai at redhat.com>
    Reviewed-on: http://review.gluster.org/11260
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Raghavendra G <rgowdapp 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=P3C6m7Kbgx&a=cc_unsubscribe