[Gluster-users] Replication does not replicate the reference node on crash

Krzysztof Strasburger strasbur at chkw386.ch.pwr.wroc.pl
Thu Nov 5 13:27:04 UTC 2009

On Thu, Nov 05, 2009 at 01:51:20PM +0100, joel vennin wrote:
> Basic configuration:
> volume mega-replicator
>        type       cluster/replicate
>        subvolumes zbrick1 zbrick2 zbrick3
> end-volume
> The scenario:
> 1) I copy data to the gluster mount point: -> Data is copied on the 3 nodes
> [OK]
> 2) I kill zbrick2 glusterfs, I erase data on zbrick2, I remount glusterfs
> mount point, do a ls -Rl on the mount point, data is replicated to zbrick2
> [OK]
> 3) I do exactly the same thing with zbrick1, when I mount again the zbrick1,
> I do a ls -Rl on the mount point and there is nothing, the directory is
> empty.
Could you please be more precise: do you mount zbrick1 only (expected to
be empty) or the whole mega-replicator volume? Was glusterfsd restarted
on the node serving zbrick1, or was it all done on a "living body"?
These questions are possibly naive or even stupid, but many troubles result
from simple omissions...
>     So I do a ls -Rl on the zbrick2 and on zbrick3, and I get the same
> result, nothing on the mount point.
Does it mean that zbrick2 and zbrick3 became empty _after_ rebuilding
zbrick1 with ls -R? Data deleted, because empty zbrick1 was "newer"?

More information about the Gluster-users mailing list