<div dir="ltr">Hi Milos,<div><br></div><div>You can do this already, by changing the baseurl format to look like this. Note the 3.4 between glusterfs and latest.</div><div><br></div><div><div>baseurl=<a href="http://download.gluster.org/pub/gluster/glusterfs/3.4/LATEST/EPEL.repo/epel-$releasever/$basearch/">http://download.gluster.org/pub/gluster/glusterfs/3.4/LATEST/EPEL.repo/epel-$releasever/$basearch/</a></div>
</div><div><br></div><div>I tend not to have yum auto updates on anything production because even minor version upgrades can cause unforeseen problems.</div><div><br></div><div>J.</div></div><div class="gmail_extra"><br><br>
<div class="gmail_quote">On Mon, Aug 4, 2014 at 4:01 PM, Milos Kozak <span dir="ltr"><<a href="mailto:milos.kozak@lejmr.com" target="_blank">milos.kozak@lejmr.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Let me contribute to the upgrade process. In my case I ended up with the same problem, but in my case it was on testing setup. In that case the problem was caused by automatic night upgrade, which I have turned on on my Centos servers. Everytime you release new RPMs my servers automatically upgrade - with minor version it is not problem usually, but major one..<br>
<br>
So I would like to suggest to make directory hierarchy according to version .. To provide folders 3.4 / 3.5 / 3.6 / Latest in your repository as other projects do.<br>
<br>
This wont resolve this kind of issue, but when you are releasing 3.6 my servers are not going to upgrade automatically in the middle of the night.<br>
<br>
Thanks MIlos<div class="HOEnZb"><div class="h5"><br>
<br>
On 8/2/2014 4:37 PM, Pranith Kumar Karampuri wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
On 08/03/2014 01:43 AM, Tiemen Ruiten wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 08/02/14 20:12, Pranith Kumar Karampuri wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 08/02/2014 06:50 PM, Tiemen Ruiten wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
<br>
I'm cross-posting this from ovirt-users:<br>
<br>
I have an oVirt environment backed by a two-node Gluster-cluster.<br>
Yesterday I decided to upgrade to from GlusterFS 3.5.1 to 3.5.2, but<br>
that caused the gluster daemon to stop and now I have several lines<br>
like<br>
this in my log for the volume that hosts the VM images, called vmimage:<br>
</blockquote>
Did the upgrade happen when the volume is still running?<br>
</blockquote>
Yes...<br>
</blockquote>
I guess we need to document upgrade process if not already done.<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[2014-08-02 12:56:20.994767] E<br>
[afr-self-heal-common.c:233:<u></u>afr_sh_print_split_brain_log]<br>
0-vmimage-replicate-0: Unable to self-heal contents of<br>
'f09c211d-eb49-4715-8031-<u></u>85a5a8f39f18' (possible split-brain). Please<br>
delete the file from all but the preferred subvolume.- Pending<br>
matrix: [<br>
[ 0 408 ] [ 180 0 ] ]<br>
</blockquote>
This is the document that talks about how to resolve split-brains in<br>
gluster.<br>
<a href="https://github.com/gluster/glusterfs/blob/master/doc/split-brain.md" target="_blank">https://github.com/gluster/<u></u>glusterfs/blob/master/doc/<u></u>split-brain.md</a><br>
</blockquote>
OK, I will try that.<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
What I would like to do is the following, since I'm not 100% happy<br>
anyway with how the volume is setup:<br>
<br>
- Stop VDSM on the oVirt hosts / unmount the volume<br>
- Stop the current vmimage volume and rename it<br>
</blockquote>
Is this a gluster volume? gluster volumes can't be renamed..<br>
</blockquote>
That surprise me: in the man page I find this:<br>
<br>
volume rename <VOLNAME> <NEW-VOLNAME><br>
Rename the specified volume.<br>
</blockquote>
One more documentation bug :-(<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- Create a new vmimage volume<br>
- Copy the images from one of the nodes<br>
</blockquote>
where will these images be copied to? on to the gluster mount? if yes<br>
then there is no need to sync.<br>
</blockquote>
OK, I will try to resolve with the guide for split-brain scenarios first.<br>
</blockquote>
Let us know if you have any doubts in this document.<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- Start the volume and let it sync<br>
- Restart VDSM / mount the volume<br>
<br>
Is this going to work? Or is there critical metadata that will not be<br>
transferred with these steps?<br>
<br>
Tiemen<br>
<br>
<br>
</blockquote></blockquote></blockquote>
<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>
</blockquote>
______________________________<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>