<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>reset brick is another way of replacing a brick. this usually
helpful, when you want to replace the brick with same name. You
can find the documentation here
<a class="moz-txt-link-freetext" href="https://docs.gluster.org/en/latest/release-notes/3.9.0/#introducing-reset-brick-command">https://docs.gluster.org/en/latest/release-notes/3.9.0/#introducing-reset-brick-command</a>.</p>
<p> In your case, I think you can use replace brick. So you can
initiate a reset-brick start, then you have to replace your failed
disk and create new brick with same name . Once you have healthy
disk and brick, you can commit the reset-brick.</p>
<p><br>
</p>
<p>Let's know if you have any question,</p>
<p><br>
</p>
<p>Rafi KC<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 4/10/19 3:39 PM, David Spisla wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJyj9j_A-umyiLgqeJBvgGFBEeDH2CbU5iPUpedb+2JiMywHjg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div>Hello Martin,</div>
<div><br>
</div>
<div>look here:</div>
<div><a
href="https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.4/pdf/administration_guide/Red_Hat_Gluster_Storage-3.4-Administration_Guide-en-US.pdf"
moz-do-not-send="true">https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.4/pdf/administration_guide/Red_Hat_Gluster_Storage-3.4-Administration_Guide-en-US.pdf</a></div>
<div>on page 324. There is a manual how to replace a brick in
case of a hardware failure</div>
<div><br>
</div>
<div>Regards</div>
<div>David Spisla<br>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Am Mi., 10. Apr. 2019 um
11:42 Uhr schrieb Martin Toth <<a
href="mailto:snowmailer@gmail.com" moz-do-not-send="true">snowmailer@gmail.com</a>>:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi
all,<br>
<br>
I am running replica 3 gluster with 3 bricks. One of my
servers failed - all disks are showing errors and raid is in
fault state.<br>
<br>
Type: Replicate<br>
Volume ID: 41d5c283-3a74-4af8-a55d-924447bfa59a<br>
Status: Started<br>
Number of Bricks: 1 x 3 = 3<br>
Transport-type: tcp<br>
Bricks:<br>
Brick1: node1.san:/tank/gluster/gv0imagestore/brick1<br>
Brick2: node2.san:/tank/gluster/gv0imagestore/brick1 <—
this brick is down<br>
Brick3: node3.san:/tank/gluster/gv0imagestore/brick1<br>
<br>
So one of my bricks is totally failed (node2). It went down
and all data are lost (failed raid on node2). Now I am running
only two bricks on 2 servers out from 3.<br>
This is really critical problem for us, we can lost all data.
I want to add new disks to node2, create new raid array on
them and try to replace failed brick on this node. <br>
<br>
What is the procedure of replacing Brick2 on node2, can
someone advice? I can’t find anything relevant in
documentation.<br>
<br>
Thanks in advance,<br>
Martin<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank"
moz-do-not-send="true">Gluster-users@gluster.org</a><br>
<a
href="https://lists.gluster.org/mailman/listinfo/gluster-users"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.gluster.org/mailman/listinfo/gluster-users</a></blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Gluster-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a>
<a class="moz-txt-link-freetext" href="https://lists.gluster.org/mailman/listinfo/gluster-devel">https://lists.gluster.org/mailman/listinfo/gluster-devel</a></pre>
</blockquote>
</body>
</html>