Alastair Neil
2016-Mar-16 20:54 UTC
[Gluster-users] How to recover after one node breakdown
hopefully you have a back up of /var/lib/glusterd/glusterd.info and /var/lib/glusterd/peers, if so I think you can copy them back to and restart glusterd and the volume info should get populated from the other node. If not you can probably reconstruct these from these files on the other node. i.e: On the unaffected node the peers directory should have an entry for the failed node containing the uuid of the failed node. The glusterd.info file should enable you to recreate the peer file on the failed node. On 16 March 2016 at 09:25, songxin <songxin_1980 at 126.com> wrote:> Hi, > Now I face a problem. > Reproduc step is as below. > 1.I create a replicate volume using two brick on two board > 2.start the volume > 3.one board is breakdown and all > files in the rootfs ,including /var/lib/glusterd/*,are lost. > 4.reboot the board and ip is not change. > > My question: > How to recovery the replicate volume? > > Thanks, > Xin > > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160316/ef38b986/attachment.html>
Thank you very much for your reply. In fact it is that I use a new node ,of which rootfs is new , to replace the failed node. And the new node has same IP address with the failed one. The brick is on a external hard disk.Because the hard disk is mounted on the node ?so the data on the brick of failed node will not be loss but may be async with the brick of good node.And the brick of failed node will be mounted on the new node. Now my recovery steps is run some glusterfs command on good node as below, after starting the glusterd on new node. 1.remove brick of new node from volume(the volume type is changed from replicate to distribute) 2.peer detach the new node ip(the new node ip is same as failed node) 3.peer probe the new node ip 3.add brick of new node to volume(the volume type is change to replicate) But many problem,like data async or peer state is error etc, will happen. My question is below. Could I run some glusterfs command on good node to recover the replicate volume? if I don't copy the files ,including glusterd.info and other files,from good node to new node. Thanks Xin ???? iPhone> ? 2016?3?17??04:54?Alastair Neil <ajneil.tech at gmail.com> ??? > > hopefully you have a back up of /var/lib/glusterd/glusterd.info and /var/lib/glusterd/peers, if so I think you can copy them back to and restart glusterd and the volume info should get populated from the other node. If not you can probably reconstruct these from these files on the other node. > > i.e: > On the unaffected node the peers directory should have an entry for the failed node containing the uuid of the failed node. The glusterd.info file should enable you to recreate the peer file on the failed node. > > > On 16 March 2016 at 09:25, songxin <songxin_1980 at 126.com> wrote: >> Hi, >> Now I face a problem. >> Reproduc step is as below. >> 1.I create a replicate volume using two brick on two board >> 2.start the volume >> 3.one board is breakdown and all >> files in the rootfs ,including /var/lib/glusterd/*,are lost. >> 4.reboot the board and ip is not change. >> >> My question: >> How to recovery the replicate volume? >> >> Thanks, >> Xin >> >> >> >> >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users at gluster.org >> http://www.gluster.org/mailman/listinfo/gluster-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160317/37110589/attachment.html>