[Gluster-users] Can't replace dead peer/brick

[Bryan Murphy]

OK, I saw this but was duped by this (the first line):

*If your newly installed server has the same hostname as the former server*

I'll try to work through this document.  The server is in a cloud
environment and the way it was setup prevents it from having the same
hostname.  I can do this via hostnames, but I'll have to provision a new
cluster.

Bryan

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
>
>
>
> --
> Vikas Gorur
> Engineer - Gluster
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20110916/b16f61b9/attachment.html>