I have performed an upgrade using RPM packages and I had to stop the volume and run glusterd with the upgrade option in order to see my logs free of warnings and misleading messages. First of all, I would try to increase the verbosity of (at least) the brick logs. a. On 03/01/2013 05:41 ??, Thomas Wakefield wrote: > Help please- > > Last night I tried to upgrade from 3.2.5 to 3.3.1 and had no success > and rolled back to 3.2.5. > > I followed the instructions for the upgrade as exactly as possible, > but don't understand this section: > > 5) If you have installed from RPM, goto 6). Else, start glusterd > in upgrade mode. glusterd terminates after it performs the > necessary steps for upgrade. Re-start glusterd normally after > this termination. Essentially this process boils down to: > > a) killall glusterd > > b) glusterd --xlator-option *.upgrade=on -N > > > I used the yum gluster repo which I thought would be the easiest way. > I also tried an RPM install and no success. I could start the > volume, but none of the bricks would be online. They were all listed > as N in the online column of a "gluster volume info" output. Very > little help from the error logs. > > > Any thoughts? > > Thomas > > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-users -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130103/6dc33031/attachment-0001.html>
