Bug 1256243

Summary:	remove-brick: avoid mknod op falling on decommissioned brick even after fix-layout has happened on parent directory
Product:	[Community] GlusterFS	Reporter:	Susant Kumar Palai <spalai>
Component:	distribute	Assignee:	Susant Kumar Palai <spalai>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, rgowdapp
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1256702 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:33:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1256702

Description Susant Kumar Palai 2015-08-24 07:17:32 UTC

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.

Comment 1 Anand Avati 2015-08-25 08:53:51 UTC

COMMIT: http://review.gluster.org/11998 committed in master by Raghavendra G (rgowdapp) 
------
commit 90c7c30c3aa9417793ae972b2b9051bc5200e7e4
Author: Susant Palai <spalai>
Date:   Mon Aug 24 03:04:41 2015 -0400

    cluster/dht: avoid mknod on decommissioned brick
    
    Change-Id: I8c39ce38e257758e27e11ccaaff4798138203e0c
    BUG: 1256243
    Signed-off-by: Susant Palai <spalai>
    Reviewed-on: http://review.gluster.org/11998
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Raghavendra G <rgowdapp>

Comment 2 Kaleb KEITHLEY 2015-10-22 17:00:12 UTC

changing version to mainline in order to retire pre-release.

If you know the appropriate, correct version for this bug, please
set it.

Comment 3 Kaleb KEITHLEY 2015-10-22 17:06:51 UTC

changing version to mainline in order to retire pre-release.

If you know the appropriate, correct version for this bug, please
set it.

Comment 4 Kaleb KEITHLEY 2015-10-22 17:11:18 UTC

changing version to mainline in order to retire pre-release.

If you know the appropriate, correct version for this bug, please
set it.

Comment 5 Niels de Vos 2016-06-16 13:33:12 UTC

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 [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user