Bug 868314

Summary:	replace-brick should be able to continue
Product:	[Community] GlusterFS	Reporter:	Joe Julian <joe>
Component:	core	Assignee:	krishnan parthasarathi <kparthas>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	low
Version:	3.3.0	CC:	bugs, gluster-bugs, mailbox, nsathyan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-12-14 19:40:29 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 Joe Julian 2012-10-19 13:34:38 UTC

In the event that a replace-brick operation fails midway through for whatever reason, power failure, or a bug that causes the inode table to be walked to the end of time requiring the process to be killed, you should be able to restart the process by issuing the replace-brick..start command again. It should also restart the process automatically when glusterd is started.

Comment 1 Amar Tumballi 2012-10-22 02:37:52 UTC

Joe,
 we will try to address this, meantime, any thoughts on http://lists.gnu.org/archive/html/gluster-devel/2012-10/msg00050.html ?

Comment 2 Niels de Vos 2014-11-27 14:54:03 UTC

The version that this bug has been reported against, does not get any updates from the Gluster Community anymore. Please verify if this report is still valid against a current (3.4, 3.5 or 3.6) release and update the version, or close this bug.

If there has been no update before 9 December 2014, this bug will get automatocally closed.