Red Hat Bugzilla – Bug 868314
replace-brick should be able to continue
Last modified: 2015-11-03 18:04:50 EST
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.
we will try to address this, meantime, any thoughts on http://lists.gnu.org/archive/html/gluster-devel/2012-10/msg00050.html ?
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.