<div dir="ltr">Side note: The same annoying conversions seems to happen when using Skype.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jan 23, 2013 at 5:29 PM, Toby Corkindale <span dir="ltr"><<a href="mailto:toby.corkindale@strategicdata.com.au" target="_blank">toby.corkindale@strategicdata.com.au</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 24/01/13 10:57, Joe Julian wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 01/23/2013 03:43 PM, Toby Corkindale wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
Last night I attempted to upgrade some GlusterFS servers from 3.2.x to<br>
3.3.1.<br>
<br>
The upgrade did NOT go smoothly, and I'm quite disappointed in the<br>
documentation for the upgrade as it was quite erroneous.<br>
<br>
I followed this guide:<br>
<a href="http://www.gluster.org/2012/05/upgrading-to-glusterfs-3-3-0/" target="_blank">http://www.gluster.org/2012/<u></u>05/upgrading-to-glusterfs-3-3-<u></u>0/</a><br>
<br>
The part I take issue with is step 5, which mentions:<br>
glusterd –xlator-option *.upgrade=on -N<br>
<br>
That command very definitely does not run successfully.<br>
Reading the docs and the comments made it clear that a hypen was<br>
missing, however even the following command only returns an error:<br>
<br>
glusterd --xlator-option *.upgrade=on -N<br>
<br>
I then took a guess based on the docs, and tried this instead:<br>
<br>
glusterd --xlator-option*.upgrade=on -N<br>
<br>
That command exited without an error message, so initially I thought<br>
it had succeeded; however when I checked the contents of the vol<br>
files, I found that they had not been changed or upgraded at all.<br>
In /var/log/gluster/ there was a file called<br>
"--xlator-option*.upgrade=on.<u></u>log"<br>
and it just contained errors about invalid mount points.<br>
<br>
<br>
Sooooooooo my questions are:<br>
1) what is the correct way to upgrade a 3.2 cluster to 3.3?<br>
2) What are the consequences of having effectively skipped whatever<br>
that command was meant to do?<br>
3) how can an eight month old wiki page on the upgrade be so wrong and<br>
yet no-one has noticed??<br>
<br>
</blockquote>
1) From the RPM scripts, I copied:<br>
<br>
glusterd --xlator-option *.upgrade=on -N<br>
<br>
You didn't specify what error you noticed, so I can't go any further<br>
with that question.<br>
</blockquote>
<br></div></div>
I had a look at my bash history, and it appears that the command I was entering was using two hypens, but the second one was the unicode hypen and the first was the keyboard hyphen. (ie. I had copied and pasted, then added an extra hyphen). That'll explain the errors I was seeing.<br>
<br>
Re-running the command, as copied from your email above, does seem to work fine, and does modify the .vol files in /var/lib/glusterd<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2) The consequences I pulled from that same "wiki" page (actually it's a<br>
wordpress article), "This will re-generate volume files with the new<br>
‘index’ translator which is needed for features like pro-active self<br>
heal in 3.3.0."<br>
</blockquote>
<br></div>
Ah OK, I was wondering what happens if you don't have that stuff.. It sounds like the self-healing will be broken, but not other stuff?<div class="im"><br>
<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
3) I suspect the version migration from the former wordpress to the<br>
current did that stupid hyphen replacement thing that plagues many tech<br>
articles all over the internet. For some reason that software likes to<br>
convert "--" to "&hyph;". Another reason that nobody's complained may be<br>
that the RPM packaging does that for you so it's superfluous to those users.<br>
<br>
That should get fixed though. Thanks for pointing it out.<br>
</blockquote>
<br></div>
Thanks for dealing with the bug report quickly and helpfully.<div class="HOEnZb"><div class="h5"><br>
<br>
-Toby<br>
<br>
______________________________<u></u>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://supercolony.gluster.<u></u>org/mailman/listinfo/gluster-<u></u>users</a><br>
</div></div></blockquote></div><br></div>