[Bugs] [Bug 1256243] New: remove-brick: avoid mknod op falling on decommissioned brick even after fix-layout has happened on parent directory

[bugzilla at redhat.com]

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

            Bug ID: 1256243
           Summary: remove-brick: avoid mknod op falling on decommissioned
                    brick even after fix-layout has happened on parent
                    directory
           Product: GlusterFS
           Version: pre-release
         Component: distribute
          Assignee: bugs at gluster.org
          Reporter: spalai at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:
Because of stale-layout issue, a mknod op may fall on decommissioned brick even
after the parent layout is fixed.

Version-Release number of selected component (if applicable):


How reproducible:
Quite frequent with nfs mount 

Steps to Reproduce:
1. create distribute volume with more than one brick
2. remove one of the brick
3. post remove-brick do large number of mknod call. 


Actual results:
Some files are left on the removed-brick post remove-brick commit.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.