On 05/07/2011 12:58 PM, Nobodys Home wrote:
Hello, I was "afraid" to delete anything since I have seen no DR docs related to this state. We did seem to reslove the situation however: 1. Did md5sum's of all file in /etc/glusterd and /etc/glusterfs on gbe02 and compared results to other 7 peers. 2. Noticed that the info file on gbe02 had a different Status then all others. 3. Noticed that the Status line in vols/peers/* differed on gbe02 while again... the other members had all identical files. This entire problem occured while we were shutting down our servers for maintenance. We knew there were no writes occuring during this time. We decided to update gbe02's inof and vol/peers/* files to match the rest of the group and restart glusterd on it. Wala... It joined the others.
Hmmm ... are you using gluster 3.1.x or 3.2.x? Are you using volume files you are crafting or modifying by hand?
-- Joseph Landman, Ph.D Founder and CEO Scalable Informatics, Inc. email: landman@xxxxxxxxxxxxxxxxxxxxxxx web : http://scalableinformatics.com http://scalableinformatics.com/sicluster phone: +1 734 786 8423 x121 fax : +1 866 888 3112 cell : +1 734 612 4615
