<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 01/23/2013 03:43 PM, Toby Corkindale
wrote:<br>
</div>
<blockquote cite="mid:51007591.9030003@strategicdata.com.au"
type="cite">Hi,
<br>
Last night I attempted to upgrade some GlusterFS servers from
3.2.x to 3.3.1.
<br>
<br>
The upgrade did NOT go smoothly, and I'm quite disappointed in the
documentation for the upgrade as it was quite erroneous.
<br>
<br>
I followed this guide:
<br>
<a class="moz-txt-link-freetext" href="http://www.gluster.org/2012/05/upgrading-to-glusterfs-3-3-0/">http://www.gluster.org/2012/05/upgrading-to-glusterfs-3-3-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
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 it had succeeded; however when I checked the contents of
the vol 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.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 that command was meant to do?
<br>
3) how can an eight month old wiki page on the upgrade be so wrong
and yet no-one has noticed??
<br>
<br>
</blockquote>
1) From the RPM scripts, I copied:<br>
<pre>glusterd --xlator-option *.upgrade=on -N
</pre>
You didn't specify what error you noticed, so I can't go any further
with that question.<br>
<br>
2) The consequences I pulled from that same "wiki" page (actually
it's a wordpress article), "This will re-generate volume files with
the new ‘index’ translator which is needed for features like
pro-active self heal in 3.3.0."<br>
<br>
3) I suspect the version migration from the former wordpress to the
current did that stupid hyphen replacement thing that plagues many
tech articles all over the internet. For some reason that software
likes to convert "--" to "&hyph;". Another reason that nobody's
complained may be 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>
<pre><meta http-equiv="content-type" content="text/html; charset=windows-1252"></pre>
</body>
</html>