Bug 1143905

Summary:	Brick still there after removal
Product:	[Community] GlusterFS	Reporter:	NOVELTIS IT <sysadmin>
Component:	glusterd	Assignee:	GlusterFS Bugs list <gluster-bugs>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.5.1	CC:	amukherj, bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-23 13:11:56 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:

Description NOVELTIS IT 2014-09-18 08:44:57 UTC

Description of problem:
I am in a 3 hosts/3 bricks cluster configuration, with a single distributed volume.

Because I would like to change the FS of my bricks from xfs to ext4 (xfs is to slow with small files) I tried to remove a brick from my volume with the command :
gluster volume remove-brick projets projet3:/glusterfs/projets-brick3/projet start
After one day of pending status, the task was successful but, when I perform a "gluster volume status", the brick is still there :
http://pastebin.com/7KZWJeet
I tried to launch the command again but I have this result :
> volume remove-brick start: failed: Incorrect brick projet3:/glusterfs/projets-brick3/projet for volume projets
I tried to launch a removal of the server which was hosting this brick :
> peer detach: failed: Brick(s) with the peer projet3 exist in cluster

Other space thing, on all mount of the volume "projets", all the folder were duplicated, whith the same content. To solve this, I remove the "projets" folder on the brick3.

I'm totaly lost. I just want to remove this brick and this host from the gluster configuration.

Thank you for your help.

Comment 1 Atin Mukherjee 2014-09-22 05:05:31 UTC

Thilam,

Until you commit remove-brick transaction, brick doesn't go away, remobe-brick commit should follow remove-brick start once the status is completed. Please try the mentioned steps and close this bug accordingly.

Thanks,
Atin

Comment 2 NOVELTIS IT 2014-09-23 13:11:56 UTC

Hi,

It is now solved. Commit did not work.

I had to stop all glusterfs daemon on all nodes + manually kill remaining processes.

Then start again all daemons and commit the removal.

Regards,
T-