Hide Forgot
steps to reproduce: 1. create a volume of type 'stripe-replicate' (or 'distribute-stripe-replicate') 2. do a 'gluster peer probe NEW-SERVER' 3. new server's volume is not same as it should be. Solution: send 'stripe-count' (which is written as part of volume information in /etc/glusterd/vols/<volname>/info) to peer after the handshake is complete.
CHANGE: http://review.gluster.com/369 (without which, if a peer is added after volume of type 'stripe-replica') merged in master by Anand Avati (avati)
Its working fine now. Commands: gluster volume create new stripe 2 replica 2 10.1.11.73:/export/mirror1 10.1.11.74:/export/mirror1 10.1.11.73:/export/mirror2 10.1.11.74:/export/mirror2 Creation of volume new has been successful. Please start the volume to access data. [root@Centos1 ~]# gluster peer probe 10.1.11.75 Probe successful Volfile: volume new-client-0 type protocol/client option remote-host 10.1.11.73 option remote-subvolume /export/mirror1 option transport-type tcp end-volume volume new-client-1 type protocol/client option remote-host 10.1.11.74 option remote-subvolume /export/mirror1 option transport-type tcp end-volume volume new-client-2 type protocol/client option remote-host 10.1.11.73 option remote-subvolume /export/mirror2 option transport-type tcp end-volume volume new-client-3 type protocol/client option remote-host 10.1.11.74 option remote-subvolume /export/mirror2 option transport-type tcp end-volume volume new-replicate-0 type cluster/replicate subvolumes new-client-0 new-client-1 end-volume volume new-replicate-1 type cluster/replicate subvolumes new-client-2 new-client-3 end-volume volume new-stripe-0 type cluster/stripe subvolumes new-replicate-0 new-replicate-1 end-volume