Re: [Gluster-users] Recovering lost node in dispersed volume

2016-09-22 Thread Tony Schreiner
Thanks for that advice. It worked. Setting the UUID in glusterd.info was the bit I missed. It seemed to work without the setfattr step in my particular case. On Thu, Sep 22, 2016 at 11:05 AM, Serkan Çoban wrote: > Here are the steps for replacing a failed node: > > > 1-

Re: [Gluster-users] Recovering lost node in dispersed volume

2016-09-22 Thread Serkan Çoban
Here are the steps for replacing a failed node: 1- In one of the other servers run "grep thaila /var/lib/glusterd/peers/* | cut -d: -f1 | cut -d/ -f6" and note the UUID 2- stop glusterd on failed server and add "UUID=uuid_from_previous step" to /var/lib/glusterd/glusterd.info and start glusterd

[Gluster-users] Recovering lost node in dispersed volume

2016-09-22 Thread Tony Schreiner
I set uo a dispersed volume with 1 x (3 + 1) nodes ( i do know that 3+1 is not optimal). Originally created in version 3.7 but recently upgraded without issue to 3.8. # gluster vol info Volume Name: rvol Type: Disperse Volume ID: e8f15248-d9de-458e-9896-f1a5782dcf74 Status: Started Snapshot