<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">I would like to follow up on my
question regarding an upgrade from 3.2.6 to 3.4.2. <br>
Can anybody tell me whether I'm doing something completely wrong?
Am I trying to skip too many versions of gluster in my upgrade? Is
CentOS 5 too old for this?<br>
<br>
Thanks,<br>
<br>
Dmitry <br>
<br>
On 2/18/2014 2:51 PM, Dmitry Kopelevich wrote:<br>
</div>
<blockquote cite="mid:5303B9CB.7000800@che.ufl.edu" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
I am attempting to upgrade my GlusterFS from 3.2.6 to 3.4.2 using
the instructions posted at <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://vbellur.wordpress.com/2012/05/31/upgrading-to-glusterfs-3-3">http://vbellur.wordpress.com/2012/05/31/upgrading-to-glusterfs-3-3</a>.
These guidelines are for an upgrade to 3.3 but it is stated at <a
moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://vbellur.wordpress.com/2013/07/15/upgrading-to-glusterfs-3-4">http://vbellur.wordpress.com/2013/07/15/upgrading-to-glusterfs-3-4</a>
that they can also be used to upgrade to 3.4.0. So I was hoping
that they would also work with an upgrade to 3.4.2. <br>
<br>
I'm running CentOS 5 and installed the following rpms on the
gluster servers:<br>
<br>
<tt>glusterfs-libs-3.4.2-1.el5.x86_64.rpm</tt><tt><br>
</tt><tt> glusterfs-3.4.2-1.el5.x86_64.rpm</tt><tt><br>
</tt><tt> glusterfs-fuse-3.4.2-1.el5.x86_64.rpm</tt><tt><br>
</tt><tt> glusterfs-cli-3.4.2-1.el5.x86_64.rpm</tt><tt><br>
</tt><tt> glusterfs-server-3.4.2-1.el5.x86_64.rpm </tt><tt><br>
</tt><tt> glusterfs-rdma-3.4.2-1.el5.x86_64.rpm</tt><tt><br>
</tt><tt> glusterfs-geo-replication-3.4.2-1.el5.x86_64.rpm</tt><br>
<br>
According to the installation guidelines, installation from rpms
should automatically copy the files from /etc/glusterd to
/var/lib/glusterd. This didn't happen for me -- the directory
/var/lib/glusterd contained only empty subdirectories. But the
content of /etc/glusterd directory has moved to
/etc/glusterd/glusterd. <br>
<br>
So, I decided to manually copy files from /etc/glusterd/glusterd
to /var/lib/glusterd and follow step 5 of the installation
guidelines (which was supposed to be skipped when installing from
rpms):<br>
<br>
<tt>glusterd --xlator-option *.upgrade=on -N</tt><tt><br>
<br>
</tt>This didn't work (error message: glusterd: No match)<font
face="sans-serif"><tt><br>
<br>
<font face="sans-serif">Then I t<tt><font face="sans-serif">ried</font></tt><tt><font
face="sans-serif"> specifyin<tt><font face="sans-serif">g
explicitly the name of my volu<tt><font
face="sans-serif">me:</font></tt></font></tt></font></tt></font><br>
<br>
</tt><tt>glusterd --xlator-option </tt></font><tt><tt><volume></tt></tt><font
face="sans-serif"><tt>.upgrade=on -N</tt></font><tt><br>
</tt><tt><br>
</tt>This lead to the following messages in file
etc-glusterfs-glusterd.vol.log:<br>
<br>
<tt>[</tt><tt>2014-02-18 17:22:27.146449] I [glusterd.c:961:init]
0-management: Using /var/lib/glusterd as working directory</tt><tt><br>
</tt><tt>[2014-02-18 17:22:27.149097] I
[socket.c:3480:socket_init] 0-socket.management: SSL support is
NOT enabled </tt><tt><br>
</tt><tt>[2014-02-18 17:22:27.149126] I
[socket.c:3495:socket_init] 0-socket.management: using system
polling thread</tt><tt><br>
</tt><tt>[2014-02-18 17:22:29.282665] I
[glusterd-store.c:1339:glusterd_restore_op_version] 0-glusterd:
retrieved op-version: 1</tt><tt><br>
</tt><tt>[2014-02-18 17:22:29.283478] E
[glusterd-store.c:1858:glusterd_store_retrieve_volume] 0-:
Unknown key: brick-0</tt><tt><br>
</tt><tt>[2014-02-18 17:22:29.283513] E
[glusterd-store.c:1858:glusterd_store_retrieve_volume] 0-:
Unknown key: brick-1</tt><tt><br>
</tt><tt>[2014-02-18 17:22:29.283534] E
[glusterd-store.c:1858:glusterd_store_retrieve_volume] 0-:
Unknown key: brick-2</tt><br>
... <br>
and so on for all other bricks.<br>
<br>
After that, files nfs.log, glustershd.log, and
etc-glusterfs-glusterd.vol.log get filled with a large number of
warning messages and nothing else seems to happen. The following
messages appear to be relevant:<br>
<br>
- Files nfs.log, glustershd.log:<br>
<br>
<tt>2014-02-18 15:58:01.889847] W
[rdma.c:1079:gf_rdma_cm_event_handler] 0-data-volume-client-2:
cma event RDMA_CM_EVENT_ADDR_ERROR, error -2 (me: peer:)<br>
</tt><br>
(the name of my volume is data-volume and its transport type is
RDMA)<br>
<br>
- File etc-glusterfs-glusterd.vol.log<br>
<br>
<tt>[2014-02-18 17:22:33.322565] W [socket.c:514:__socket_rwv]
0-management: readv failed (No data available)</tt><br>
<br>
Also, for some reason the time stamps in the log files are
incorrect.<br>
<br>
Any suggestions for fixing this would be greatly appreciated.<br>
<br>
Thanks,<br>
<br>
Dmitry<br>
<pre class="moz-signature" cols="72">--
Dmitry Kopelevich
Associate Professor
Chemical Engineering Department
University of Florida
Gainesville, FL 32611
Phone: (352)-392-4422
Fax: (352)-392-9513
E-mail: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:dkopelevich@che.ufl.edu">dkopelevich@che.ufl.edu</a>
</pre>
</blockquote>
<br>
</body>
</html>