Red Hat Bugzilla – Bug 1256243
remove-brick: avoid mknod op falling on decommissioned brick even after fix-layout has happened on parent directory
Last modified: 2016-06-16 09:33:12 EDT
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):
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.
Some files are left on the removed-brick post remove-brick commit.
COMMIT: http://review.gluster.org/11998 committed in master by Raghavendra G (firstname.lastname@example.org)
Author: Susant Palai <email@example.com>
Date: Mon Aug 24 03:04:41 2015 -0400
cluster/dht: avoid mknod on decommissioned brick
Signed-off-by: Susant Palai <firstname.lastname@example.org>
Tested-by: NetBSD Build System <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Raghavendra G <email@example.com>
changing version to mainline in order to retire pre-release.
If you know the appropriate, correct version for this bug, please
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.
glusterfs-3.8.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.