On Fri, Sep 16, 2011 at 4:17 PM, Bryan Murphy <bmurphy1976 at gmail.com> wrote: > On Fri, Sep 16, 2011 at 4:02 PM, Vikas Gorur <vikas at gluster.com> wrote: > >> Brian, >> >> Replace-brick is not what you need here. Replace-brick is designed to be >> used for a planned decommissioning of a node and migration of data from it >> to a new node. You can only use replace-brick when both the source and the >> target servers are up and running. >> >> If you have a catastrophic failure where one of the servers gets its OS >> disk completely wiped, you need to do this: >> >> >> http://europe.gluster.org/community/documentation/index.php/Gluster_3.2:_Brick_Restoration_-_Replace_Crashed_Server >> >> I finally got around to following up on this. I provisioned a new cluster (using static hostnames), killed a server, replaced it, assigned the old hostname and guid and am now rebuilding the cluster successfully. Thanks for the help, Bryan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gluster.org/pipermail/gluster-users/attachments/20110920/240ea1bb/attachment.htm>
