[Gluster-devel] replicate data between 2 servers and 1 client

[Krishna Srinivas]

On Fri, Feb 13, 2009 at 1:50 PM, Alain Gonzalez <alaingonza at gmail.com> wrote:
> I changed vol files, because I need data replicated on three machine (two
> servers and one client). If I changed data on 1 machine, data must be
> changed on the other two machines...
>
> My actual vol file:
>
> Server1:
>
> volume brick
>  type storage/posix
>  option directory /home/export/
> end-volume
>
>
> ### Add network serving capability to above brick.
> volume server
>  type protocol/server
>  option transport-type tcp
>  subvolumes brick
>  option auth.addr.brick.allow * # Allow access to "brick" volume
> end-volume
>
> Server2
>
> volume brick
>  type storage/posix
>  option directory /home/export/
> end-volume
>
> ### Add network serving capability to above brick.
> volume server
>  type protocol/server
>  option transport-type tcp
>  subvolumes brick
>  option auth.addr.brick.allow * # Allow access to "brick" volume
> end-volume
>
> Client:
>
> ### Add client feature and attach to remote subvolume of server1
> volume brick1
>  type protocol/client
>  option transport-type tcp
>  option remote-host 192.168.240.227      # IP address of the remote brick
>  option remote-subvolume brick           # name of the remote volume
> end-volume
>
> ### Add client feature and attach to remote subvolume of server2
> volume brick2
>  type protocol/client
>  option transport-type tcp
>  option remote-host 192.168.240.228      # IP address of the remote brick
>  option remote-subvolume brick           # name of the remote volume
> end-volume
>
> volume afr
>  type cluster/afr
>  subvolumes brick1 brick2
> end-volume
>
> Raghavendra G said me that in Glusterfs 2.0 requires posix-locks. I proved
> changed "type storage/posix" for "type features/posix-locks" but not working
> correctly.
>


You need to have a separate "features/locks" translator between
"storage/posix" and "protocol/server" volumes.