Bug 764189 (GLUSTER-2457)

Summary:	remove-brick command should migrate data
Product:	[Community] GlusterFS	Reporter:	William L. Sebok <wls>
Component:	cli	Assignee:	Amar Tumballi <amarts>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	mainline	CC:	gluster-bugs, jdarcy, lopresti, vraman
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description William L. Sebok 2011-02-23 18:52:49 UTC

There should be and option in "remove-brick" command (or some similar command) to migrate the data in a brick to other bricks before removing that brick. This would be *extremely* useful in dealing with a distributed/replicated filesystem with a computer and/or brick that is dead or likely to be down for an extended period (I configure bricks to be replicated between different computers). The remove-brick command on startup could make an estimate whether the data would fit on the remaining bricks. If after the migration started it turned out that the data really does not all fit there would still would not be any loss as long as the last file movement wasn't completely committed.  The command then could be aborted.

Comment 1 Amar Tumballi 2011-07-06 09:21:32 UTC


*** This bug has been marked as a duplicate of bug 1952 ***