Thank you very much for your reply. 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
|
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users