<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 07/29/2016 11:08 PM, Richard Klein
(RSI) wrote:<br>
</div>
<blockquote
cite="mid:D81F3C262184034786211E9811567A9BB520F3403E@RSIEXCH.RSITEX.COM"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
p.yiv5393753197msonormal, li.yiv5393753197msonormal, div.yiv5393753197msonormal
{mso-style-name:yiv5393753197msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
p.yiv5393753197msochpdefault, li.yiv5393753197msochpdefault, div.yiv5393753197msochpdefault
{mso-style-name:yiv5393753197msochpdefault;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
span.yiv5393753197msohyperlink
{mso-style-name:yiv5393753197msohyperlink;}
span.yiv5393753197msohyperlinkfollowed
{mso-style-name:yiv5393753197msohyperlinkfollowed;}
span.yiv5393753197emailstyle17
{mso-style-name:yiv5393753197emailstyle17;}
p.yiv5393753197msonormal1, li.yiv5393753197msonormal1, div.yiv5393753197msonormal1
{mso-style-name:yiv5393753197msonormal1;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
span.yiv5393753197msohyperlink1
{mso-style-name:yiv5393753197msohyperlink1;
color:blue;
text-decoration:underline;}
span.yiv5393753197msohyperlinkfollowed1
{mso-style-name:yiv5393753197msohyperlinkfollowed1;
color:purple;
text-decoration:underline;}
span.yiv5393753197emailstyle171
{mso-style-name:yiv5393753197emailstyle171;
font-family:"Calibri","sans-serif";
color:windowtext;}
p.yiv5393753197msochpdefault1, li.yiv5393753197msochpdefault1, div.yiv5393753197msochpdefault1
{mso-style-name:yiv5393753197msochpdefault1;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Calibri","sans-serif";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas","serif";
color:black;}
span.EmailStyle30
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:361248423;
mso-list-type:hybrid;
mso-list-template-ids:-795203952 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thank
you very much for the information. I have read the
documentation link you have listed below and just wanted
confirmation about the remove-brick process. I did not see
any documentation about the ability to use the remove-brick
stop command so that is good to know.</span></p>
</div>
</blockquote>
<br>
I'm not sure, how much testing has been done in that area. But we do
have the remove stop command, and theoretically it should work. If
you do rebalance after remove-brick stop, then again the cluster
will be load balanced if files are already migrated as part of the
remove brick operation.<br>
<br>
<br>
<blockquote
cite="mid:D81F3C262184034786211E9811567A9BB520F3403E@RSIEXCH.RSITEX.COM"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I
have a couple of related follow up questions as well:<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph"
style="text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><span
style="mso-list:Ignore">1)<span style="font:7.0pt
"Times New Roman""> </span></span></span><!--[endif]--><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Let’s
say a brick fails (hard drive goes bad). I want to replace
the bad drive with a new one and then get it back
operational in the cluster. In this case I don’t have spare
brick available so I can’t do the replace-brick. The only
procedure I have found is a blog and bug report for 3.4
about this issue with a work around. Here is the link to the
blog: <a moz-do-not-send="true"
href="https://joejulian.name/blog/replacing-a-brick-on-glusterfs-340/">https://joejulian.name/blog/replacing-a-brick-on-glusterfs-340/</a>.
Here is the link to the bug report: <a
moz-do-not-send="true"
href="https://bugzilla.redhat.com/show_bug.cgi?id=991084"><a class="moz-txt-link-freetext" href="https://bugzilla.redhat.com/show_bug.cgi?id=991084">https://bugzilla.redhat.com/show_bug.cgi?id=991084</a></a>.
My apologies if this has been addressed before but I have
searched and can’t find a solution where you just replace
the bad drive with a good one and recover. Any instructions
about this process would be appreciated.</span></p>
</div>
</blockquote>
<br>
If I understand you correctly, you want to replace a drive and
create the brick with same name. If that is the case, patch
<a class="moz-txt-link-freetext" href="http://review.gluster.org/#/c/12250/">http://review.gluster.org/#/c/12250/</a> will solve the. In fact the
patch is under review. CCing the replace brick experts to give you
more info regarding your replace queries.<br>
<br>
<br>
<blockquote
cite="mid:D81F3C262184034786211E9811567A9BB520F3403E@RSIEXCH.RSITEX.COM"
type="cite">
<div class="WordSection1">
<p class="MsoListParagraph"
style="text-indent:-.25in;mso-list:l0 level1 lfo1"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoListParagraph"
style="text-indent:-.25in;mso-list:l0 level1 lfo1"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><span
style="mso-list:Ignore">2)<span style="font:7.0pt
"Times New Roman""> </span></span></span><!--[endif]--><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Does
the rebalance process lock data files in Gluster? We are
using Gluster as primary storage in Cloudstack 4.7. If we
shrink or expand the Gluster volume we do a rebalance of the
layout and data. However, after this process we have
several VMs which have disk volumes in a read only state
like there were disk problems. Once we power cycle the VM
all is well and no data loss occurred but there seems to be
a correlation between the rebalance and the errors. I am
wondering if the rebalance process locks the data somehow
and makes it unavailable to the VM.</span></p>
</div>
</blockquote>
<br>
Rebalance process will take locks as part of the healing. But I'm
not sure whether it cause VM's to go into read-only state. The locks
will be took on directory for healing and for files during
migration, but only for a specific offset. So both should not cause
an entire file to be read-only for a long time.<br>
<br>
Can you describe your problem more ? I will try to see if there is
anything else causing the issue.<br>
<br>
<br>
Regards<br>
Rafi KC<br>
<br>
<blockquote
cite="mid:D81F3C262184034786211E9811567A9BB520F3403E@RSIEXCH.RSITEX.COM"
type="cite">
<div class="WordSection1">
<p class="MsoListParagraph"
style="text-indent:-.25in;mso-list:l0 level1 lfo1"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks
again for the response.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Richard
Klein<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">RSI<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">
Mohammed Rafi K C [<a class="moz-txt-link-freetext" href="mailto:rkavunga@redhat.com">mailto:rkavunga@redhat.com</a>] <br>
<b>Sent:</b> Friday, July 29, 2016 1:38 AM<br>
<b>To:</b> Lenovo Lastname; Richard Klein (RSI);
<a class="moz-txt-link-abbreviated" href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br>
<b>Subject:</b> Re: [Gluster-users] Clarification about
remove-brick<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>You can also see the documentation here <a
moz-do-not-send="true"
href="https://gluster.readthedocs.io/en/latest/Administrator%20Guide/Managing%20Volumes/#shrinking-volumes"><a class="moz-txt-link-freetext" href="https://gluster.readthedocs.io/en/latest/Administrator%20Guide/Managing%20Volumes/#shrinking-volumes">https://gluster.readthedocs.io/en/latest/Administrator%20Guide/Managing%20Volumes/#shrinking-volumes</a></a><o:p></o:p></p>
<p><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Rafi KC<o:p></o:p></p>
<div>
<p class="MsoNormal">On 07/29/2016 11:39 AM, Mohammed Rafi K C
wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p><o:p> </o:p></p>
<p>I will summarize the procedure for removing a brick with
description.<o:p></o:p></p>
<p><o:p> </o:p></p>
<p>1) start an add brick operation using gluster volume
remov-brick command. This command will mark the mentioned
brick as a decommissioned brick. Also, this will kick a
process that will start migrating data from the
decommissioned brick to the other bricks.<o:p></o:p></p>
<p>2) Once the migration is finished you can safely do a
remove-brick commit.<o:p></o:p></p>
<p>3) Or if you wish to stop the process and reset the
decommissioned brick, you can do remove-brick stop. This
will not migrate the data back to the decommissioned brick.
It will stay in the other bricks and the data will be still
accessible, if you want to have proper load balancing after
this, you can start rebalance process.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">4) If you
wish to do an instant remove brick you can use force option,
which will not migrate data, hence your whole data in the
removed brick will be lost from mount point.<br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal">On 07/29/2016 01:25 AM, Lenovo Lastname
wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div id="yui_3_16_0_ym19_1_1469735580774_2532">
<p class="MsoNormal" style="background:white"><span
style="font-size:6.0pt;font-family:"Helvetica","sans-serif"">I'm
using 3.7.11, this command works with me,<o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1469735580774_2531">
<p class="MsoNormal" style="background:white"><span
style="font-size:6.0pt;font-family:"Helvetica","sans-serif""><o:p> </o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1469735580774_2518">
<p class="MsoNormal" style="background:white"><span
style="font-size:6.0pt;font-family:"Helvetica","sans-serif"">!remove-brick<br
id="yui_3_16_0_ym19_1_1469735580774_2514">
[root@node2 ~]# gluster volume remove-brick v1
replica 2 192.168.3.73:/gfs/b1/v1 force<br
id="yui_3_16_0_ym19_1_1469735580774_2515">
Removing brick(s) can result in data loss. Do you
want to Continue? (y/n) y<br
id="yui_3_16_0_ym19_1_1469735580774_2516">
volume remove-brick commit force: success<o:p></o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1469735580774_2519">
<p class="MsoNormal" style="background:white"><span
style="font-size:6.0pt;font-family:"Helvetica","sans-serif""><o:p> </o:p></span></p>
</div>
<div id="yui_3_16_0_ym19_1_1469735580774_2521">
<p class="MsoNormal" style="background:white"><span
style="font-size:6.0pt;font-family:"Helvetica","sans-serif"">Don't
know about the commit thingy...<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"
style="margin-bottom:12.0pt;background:white"><span
style="font-size:6.0pt;font-family:"Helvetica","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span
style="font-size:10.0pt;font-family:"Arial","sans-serif"">On
Thursday, July 28, 2016 3:47 PM, Richard Klein
(RSI) <a moz-do-not-send="true"
href="mailto:rklein@rsitex.com"><rklein@rsitex.com></a>
wrote:</span><span
style="font-family:"Helvetica","sans-serif""><o:p></o:p></span></p>
</div>
<p class="MsoNormal"
style="margin-bottom:12.0pt;background:white"><span
style="font-family:"Helvetica","sans-serif""><o:p> </o:p></span></p>
<div>
<div id="yiv5393753197">
<div>
<div>
<div>
<p class="MsoNormal"
style="background:white"><span
style="font-family:"Helvetica","sans-serif"">We
are using Gluster 3.7.6 in a replica 2
distributed-replicate configuration.
I am wondering when we do a
remove-brick with just one brick pair
will the data be moved off the bricks
once the status show complete and then
you do the commit? Also, if you
start a remove-brick process can you
stop it? Is there an abort or stop
command or do you just don’t do the
commit?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"
style="background:white"><span
style="font-family:"Helvetica","sans-serif""> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"
style="background:white"><span
style="font-family:"Helvetica","sans-serif"">Any
help would be appreciated.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"
style="background:white"><span
style="font-family:"Helvetica","sans-serif""> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"
style="background:white"><span
style="font-family:"Helvetica","sans-serif"">Richard
Klein<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"
style="background:white"><span
style="font-family:"Helvetica","sans-serif"">RSI<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"
style="background:white"><span
style="font-family:"Helvetica","sans-serif""> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"
style="background:white"><span
style="font-family:"Helvetica","sans-serif""> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"
style="background:white"><span
style="font-family:"Helvetica","sans-serif""> <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"
style="margin-bottom:12.0pt;background:white"><span
style="font-family:"Helvetica","sans-serif""><br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a moz-do-not-send="true"
href="http://www.gluster.org/mailman/listinfo/gluster-users"
target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Gluster-users mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a></pre>
</blockquote>
<br>
</body>
</html>