<div class="gmail_quote">On Fri, Sep 16, 2011 at 4:17 PM, Bryan Murphy <span dir="ltr"><<a href="mailto:bmurphy1976@gmail.com">bmurphy1976@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div><div class="h5"><div><div class="gmail_quote">On Fri, Sep 16, 2011 at 4:02 PM, Vikas Gorur <span dir="ltr"><<a href="mailto:vikas@gluster.com" target="_blank">vikas@gluster.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Brian,</div><div><br></div>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.<div>
<br></div><div>If you have a catastrophic failure where one of the servers gets its OS disk completely wiped, you need to do this:</div><div><br></div><div><a href="http://europe.gluster.org/community/documentation/index.php/Gluster_3.2:_Brick_Restoration_-_Replace_Crashed_Server" target="_blank">http://europe.gluster.org/community/documentation/index.php/Gluster_3.2:_Brick_Restoration_-_Replace_Crashed_Server</a></div>
<div><br></div></blockquote></div></div></div></div></div></blockquote><div><br>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.</div>
<div><br>Thanks for the help,</div><div>Bryan </div></div>