This looks like your peers are in inconsistent state. I believe peer status output must be showing glusterp2 in disconnected state. Can you forcibly detach it and then attach it back to the cluster?
On Mon, Dec 14, 2015 at 9:07 AM, Thing <[email protected]> wrote: > I am attempting to create a gluster volume but get this error, > > ============ > [root@glusterp1 data1]# gluster volume create volume1 replica 3 transport > tcp glusterp1.graywitch.co.nz:/data1 glusterp2.graywitch.co.nz:/data1 > gvolume create: volume1: failed: Staging failed on > glusterp3.graywitch.co.nz. Error: Host glusterp1.graywitch.co.nz is not > in 'Peer in Cluster' st > Staging failed on glusterp2.graywitch.co.nz. Error: Host > glusterp3.graywitch.co.nz is not in 'Peer in Cluster' state > [root@glusterp1 data1]# gluster peer probe glusterp2.graywitch.co.nz > peer probe: success. Host glusterp2.graywitch.co.nz port 24007 already in > peer list > [root@glusterp1 data1]# gluster peer probe glusterp3.graywitch.co.nz > peer probe: success. Host glusterp3.graywitch.co.nz port 24007 already in > peer list > [root@glusterp1 data1]# gluster volume create volume1 replica 3 transport > tcp glusterp1.graywitch.co.nz:/data1 glusterp2.graywitch.co.nz:/data1 g > volume create: volume1: failed: Staging failed on > glusterp3.graywitch.co.nz. Error: Host glusterp1.graywitch.co.nz is not > in 'Peer in Cluster' st > Staging failed on glusterp2.graywitch.co.nz. Error: Host > glusterp3.graywitch.co.nz is not in 'Peer in Cluster' state > [root@glusterp1 data1]# ls -l > total 0 > [root@glusterp1 data1]# > ============ > > what is wrong here please? > > _______________________________________________ > Gluster-users mailing list > [email protected] > http://www.gluster.org/mailman/listinfo/gluster-users >
_______________________________________________ Gluster-users mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-users
