<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></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]-->
</head>
<body lang="EN-CA" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoPlainText">Yes. Worked perfectly. No issues. Only thing worth noting, which I knew but had forgotten about, was that I had the option lookup-unhashed off. That meant when I added the new bricks and told it to rebalance a bunch of the files became
unavailable until I re-enabled it. Makes sense though because the files wouldn’t be where they were supposed to be while it was working on rebalancing. I took the route of taking the whole cluster down, making the modifications to the vol info on each member,
then bringing it all back up.<o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="mso-fareast-language:EN-CA">From:</span></b><span lang="EN-US" style="mso-fareast-language:EN-CA"> Brandon Mackie
<br>
<b>Sent:</b> April 21, 2014 1:24 PM<br>
<b>To:</b> gluster-users@gluster.org<br>
<b>Subject:</b> RE: Upgrade from 3.3 to 3.4.3 now can't add bricks<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">A conversation with myself, but JoeJulian was kind enough to point out that it was the info file and not the vol file that wasn’t matched. Confirmed that new servers have two extra lines:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">op-version=2<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">client-op-version=2<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Which of course would cause a mismatch. I’ll take down everything tonight and see if that corrects it as it does correct it on some test servers.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="mso-fareast-language:EN-CA">From:</span></b><span lang="EN-US" style="mso-fareast-language:EN-CA">
<a href="mailto:gluster-users-bounces@gluster.org">gluster-users-bounces@gluster.org</a> [<a href="mailto:gluster-users-bounces@gluster.org">mailto:gluster-users-bounces@gluster.org</a>]
<b>On Behalf Of </b>Brandon Mackie<br>
<b>Sent:</b> April 21, 2014 1:13 PM<br>
<b>To:</b> <a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br>
<b>Subject:</b> Re: [Gluster-users] Upgrade from 3.3 to 3.4.3 now can't add bricks<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Replace “bricks” with “servers” as IRC just informed me my vocab was crossed. Anyway, I wanted to add that following
<a href="http://www.gluster.org/community/documentation/index.php/Resolving_Peer_Rejected">
http://www.gluster.org/community/documentation/index.php/Resolving_Peer_Rejected</a> I can get one brick to see it as not rejected (the brick that I peer on step 4 but the rest still see it as rejected.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="mso-fareast-language:EN-CA">From:</span></b><span lang="EN-US" style="mso-fareast-language:EN-CA">
<a href="mailto:gluster-users-bounces@gluster.org">gluster-users-bounces@gluster.org</a> [<a href="mailto:gluster-users-bounces@gluster.org">mailto:gluster-users-bounces@gluster.org</a>]
<b>On Behalf Of </b>Brandon Mackie<br>
<b>Sent:</b> April 21, 2014 12:40 PM<br>
<b>To:</b> <a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br>
<b>Subject:</b> [Gluster-users] Upgrade from 3.3 to 3.4.3 now can't add bricks<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Good afternoon folks,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Not sure if this is an occurrence of <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1072720">
https://bugzilla.redhat.com/show_bug.cgi?id=1072720</a> but cannot add new bricks to my existing cluster running under Ubuntu 12. New bricks are completely blank.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Peer probed new from a trusted member. Both sides say “Peer Rejected (Connected)” but does not migrate the peer to the other bricks. If I then clear out the newly created /var/lib/glusterd on the new brick and then restart the server then
it migrates to all bricks but all say rejected (connected) instead of just one. Confirmed not firewall as I can open a tcp port in both directions.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">A quick snap of the log on the new brick:<o:p></o:p></p>
<p class="MsoNormal"><a href="http://pastie.org/9098095">http://pastie.org/9098095</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’ve heard this means the vol file doesn’t match but this is a brand new clean server and therefore no vol file.<o:p></o:p></p>
</div>
</body>
</html>