<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt">Yes, I manually edited the file.<br><div><br><span></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;"><span>I still have one issue:</span></div><br>I see in the logs:<br><br>-datavol-dht: setattr of uid/gid on <gfid:7800cc88-1a5a-4cb6-b63d-e4b11ee9f5bb>filename.foo :<gfid:00000000-0000-0000-0000-000000000000> failed (Invalid <br><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;"><span> argument)<br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color:
transparent; font-style: normal;"><span><br></span></div><div style="color: rgb(0, 0, 0); font-size: 16px; font-family: times new roman,new york,times,serif; background-color: transparent; font-style: normal;"><span>do I need to have same uid/guid on each glusterfs server? As it seems setting uid/gid fails?</span></div><div><br></div> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <hr size="1"> <font face="Arial" size="2"> <b><span style="font-weight:bold;">From:</span></b> John Mark Walker <johnmark@gluster.org><br> <b><span style="font-weight: bold;">To:</span></b> Xset Mode <xsetmode@yahoo.com> <br><b><span style="font-weight: bold;">Cc:</span></b> gluster-users@gluster.org <br> <b><span style="font-weight: bold;">Sent:</span></b> Monday, August 19, 2013 7:51 PM<br> <b><span style="font-weight:
bold;">Subject:</span></b> Re: [Gluster-users] After Upgrade of 3.2.7 => 3.4 gluster, I cant do gluster peer probe newfreshpeer<br> </font> </div> <div class="y_msg_container"><br><div id="yiv7635680069"><div><div style="font-family:times new roman, new york, times, serif;font-size:12pt;color:#000000;"><div><br></div><hr id="yiv7635680069zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica, Arial, sans-serif;font-size:12pt;"><div style="color:#000;background-color:#fff;font-family:times new roman, new york, times, serif;font-size:12pt;"><div><span>I just edited /var/lib/glusterd/glusterd.info and restarted glusterds</span></div></div></blockquote><div><br></div><div>Just so I understand, you manually added "operating-version=2" to the glusterd.info file?<br></div><div><br></div><div>There's probably an issue with the DEB
packages for Ubuntu. I'm curious if the Debian packages on download.gluster.org have the same issue.<br></div><div><br></div><div>-JM<br></div><div><br></div><div><br></div><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica, Arial, sans-serif;font-size:12pt;"><div style="color:#000;background-color:#fff;font-family:times new roman, new york, times, serif;font-size:12pt;"><div><span><br></span></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;"><br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;"><br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times,
serif;background-color:transparent;font-style:normal;"><span>operating-version=2 and peer probe works now</span></div><div><br></div><div style="font-family:times new roman, new york, times, serif;font-size:12pt;"><div style="font-family:times new roman, new york, times, serif;font-size:12pt;"><div dir="ltr"><hr size="1"><span style="font-family:Arial;font-size:small;"> <b><span style="font-weight:bold;">From:</span></b> Xset Mode <xsetmode@yahoo.com><br> <b><b>To:</b></b> "gluster-users@gluster.org" <gluster-users@gluster.org> <br> <b><span style="font-weight:bold;">Sent:</span></b> Monday, August 19, 2013 6:11 PM<br> <b><span style="font-weight:bold;">Subject:</span></b> Re: [Gluster-users] After Upgrade of 3.2.7 => 3.4 gluster, I cant do gluster peer probe newfreshpeer<br> </span></div><div class="yiv7635680069y_msg_container"><br><div id="yiv7635680069"><div><div style="color:#000;background-color:#fff;font-family:times new roman, new
york, times, serif;font-size:12pt;">Someone has actually just done an
upgrade on an existing cluster, from
glusterfs-3.4.0-3.el6.x86_64 to glusterfs-3.4.0-8.el6.x86_64 <br>that caused the operating version to change on /var/lib/glusterd/glusterd.info operatiog-version=1 to operating-version=2<br><div><br></div>But that was RHEL based distribution<br><div><br></div>I'm running Ubuntu 13.04 using the packages from <br><div><br></div>deb http://ppa.launchpad.net/semiosis/ubuntu-glusterfs-3.4/ubuntu raring main<br><div><br></div><br>On
my old cluster nodes I have same version of packages installed, but
operating-version=1 on /var/lib/glusterd/glusterd.info file<br><div><br></div>Can I
manually edit operating-version=2 on /var/lib/glusterd/glusterd.info
file & restart glusterd on all old servers and then try<br>gluster peer probe storage8 (storage8 is the newest node without /var/lib/glusterd/glusterd.info file)<br><div><br></div><div style="font-family:times new roman, new york, times, serif;font-size:12pt;"><div style="font-family:times new roman, new york, times, serif;font-size:12pt;"><div dir="ltr"><hr size="1"><span style="font-family:Arial;font-size:small;"> <b><span style="font-weight:bold;">From:</span></b> Xset Mode <xsetmode@yahoo.com><br> <b><span style="font-weight:bold;">To:</span></b> "gluster-users@gluster.org" <gluster-users@gluster.org> <br> <b><span style="font-weight:bold;">Sent:</span></b> Monday, August 19, 2013 5:35 PM<br> <b><span style="font-weight:bold;">Subject:</span></b> Re: [Gluster-users] After Upgrade of 3.2.7 => 3.4 gluster, I cant do gluster peer probe newfreshpeer<br> </span></div><div class="yiv7635680069y_msg_container"><br><div
id="yiv7635680069"><div><div style="color:#000;background-color:#fff;font-family:times new roman, new york, times, serif;font-size:12pt;">Also in old cluster node logs I see this:<br><div><br></div>[2013-08-19
13:54:24.560339] E
[glusterd-handshake.c:900:__glusterd_mgmt_hndsk_version_cbk]
0-management: failed to validate the operating version of peer
(storage8)<div><br></div><div style="font-family:times new roman, new york, times, serif;font-size:12pt;"><div style="font-family:times new roman, new york, times, serif;font-size:12pt;"><div dir="ltr"><hr size="1"><span style="font-family:Arial;font-size:small;"> <b><span style="font-weight:bold;">From:</span></b> Xset Mode <xsetmode@yahoo.com><br> <b><span style="font-weight:bold;">To:</span></b> "gluster-users@gluster.org" <gluster-users@gluster.org> <br> <b><span style="font-weight:bold;">Sent:</span></b> Monday, August 19, 2013 4:58 PM<br> <b><span style="font-weight:bold;">Subject:</span></b> [Gluster-users] After Upgrade of 3.2.7 => 3.4 gluster, I cant do gluster peer probe newfreshpeer<br> </span></div><div class="yiv7635680069y_msg_container"><br><div id="yiv7635680069"><div><div style="color:#000;background-color:#fff;font-family:times new roman, new york, times, serif;font-size:12pt;"><div>I followed following
instructions to upgrade existing gluster cluster 3.2.7 to 3.4 gluster on Ubuntu 13.04<br></div><div><br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;">http://vbellur.wordpress.com/2012/05/31/upgrading-to-glusterfs-3-3/</div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;"><br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;">I stopped all glusterd and client processes first.</div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;"><br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times,
serif;background-color:transparent;font-style:normal;">I had to copy files from /etc/glusterd/ to /var/lib/glusterd as the location has changed in 3.4</div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;"><br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;">I also had to do the following to be able to start the volume after upgrade:</div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;"><br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;">vol=datavol; brick=/home/glusterfs; setfattr -n trusted.glusterfs.volume-id -v 0x$(grep volume-id
/var/lib/glusterd/vols/$vol/info | cut -d= -f2 | sed 's/-//g') $brick</div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;"><br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;"><br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;">All old nodes were upgraded to packages from the repository</div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;"><br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;">ii
glusterfs-client 3.4.0final-ubuntu1~raring1 amd64 clustered file-system (client package)<br>ii glusterfs-common 3.4.0final-ubuntu1~raring1 amd64 GlusterFS common libraries and translator modules<br>ii glusterfs-server 3.4.0final-ubuntu1~raring1
amd64 clustered file-system (server package)<br><div><br></div></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;"><br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;">Now when I try to add a new fresh Ubuntu 13.04 node with same packages<br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;"><br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;">ii glusterfs-client
3.4.0final-ubuntu1~raring1 amd64 clustered file-system (client package)<br>ii glusterfs-common 3.4.0final-ubuntu1~raring1 amd64 GlusterFS common libraries and translator modules<br>ii glusterfs-server 3.4.0final-ubuntu1~raring1 amd64 clustered file-system (server package)<br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;"><br></div><div style="color:rgb(0, 0,
0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;">From existing nodes trying to do:</div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;"><br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;"># gluster peer probe storage8<br>peer probe: failed: Peer storage8 is already at a higher op-version<br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;"><br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;">How can I get the op-version of existing cluster nodes to the same op-version
as the new fresh node so that gluster peer probe storage8 works from</div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;">existing nodes?</div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;"><br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;">From existing nodes I see operating-version=1</div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;"><br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;">Old nodes:</div><div style="color:rgb(0, 0,
0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;"><br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;"># /var/lib/glusterd/glusterd.info<br>UUID=ed2b70f4-b0b1-4929-a55a-2f49f4f9580f<br>operating-version=1<br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;"><br></div><div style="color:rgb(0, 0, 0);font-size:16px;font-family:times new roman, new york, times, serif;background-color:transparent;font-style:normal;"><br></div><div>Any help would be appreciated?</div></div></div></div><br>_______________________________________________<br>Gluster-users mailing list<br><a rel="nofollow" ymailto="mailto:Gluster-users@gluster.org" target="_blank"
href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br><a rel="nofollow" target="_blank" href="http://supercolony.gluster.org/mailman/listinfo/gluster-users">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><br><div><br></div></div></div></div></div></div></div><br>_______________________________________________<br>Gluster-users mailing list<br><a rel="nofollow" ymailto="mailto:Gluster-users@gluster.org" target="_blank" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br><a rel="nofollow" target="_blank" href="http://supercolony.gluster.org/mailman/listinfo/gluster-users">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><br><div><br></div></div></div></div></div></div></div><br>_______________________________________________<br>Gluster-users mailing list<br><a rel="nofollow" ymailto="mailto:Gluster-users@gluster.org" target="_blank"
href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br><a rel="nofollow" target="_blank" href="http://supercolony.gluster.org/mailman/listinfo/gluster-users">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><br><div><br></div></div></div></div></div><br>_______________________________________________<br>Gluster-users mailing list<br>Gluster-users@gluster.org<br>http://supercolony.gluster.org/mailman/listinfo/gluster-users</blockquote><div><br></div></div></div></div><br><br></div> </div> </div> </div></body></html>