Hi,<br><br>With your help I have these results: <br><br>1- Changed data on server1, data changed on server2 and client. OK<br>2- Changed data on client, data changed on server1 and server2. OK<br>3- Changed data on server2, data <b>no </b>changed on server1 and client. :(<br>
<br>config:<br><br>#server1<br><br>volume ser01<br> type storage/posix<br> option directory /home/export/<br>end-volume<br><br>volume ser011<br> type features/locks<br> subvolumes ser01<br>end-volume<br><br>### Add network serving capability to above brick.<br>
volume server<br> type protocol/server<br> option transport-type tcp<br> subvolumes ser011<br> option auth.addr.ser01.allow * # Allow access to "ser01" volume<br> option auth.addr.ser011.allow * # Allow access to "ser011" volume<br>
end-volume<br><br>#server2<br><br>volume ser02<br> type storage/posix<br> option directory /home/export/<br>end-volume<br><br>volume ser022<br> type features/locks<br> subvolumes ser02<br>end-volume<br><br>### Add network serving capability to above brick.<br>
volume server<br> type protocol/server<br> option transport-type tcp<br> subvolumes ser022<br> option auth.addr.ser02.allow * # Allow access to "ser02" volume<br> option auth.addr.ser022.allow * # Allow access to "ser022" volume<br>
end-volume<br><br>#client<br><br>### Add client feature and attach to remote subvolume of server1<br>volume cli01<br> type protocol/client<br> option transport-type tcp/client<br> option remote-host 192.168.240.227 # IP address of the remote brick<br>
option remote-subvolume ser011 # name of the remote volume<br>end-volume<br><br>### Add client feature and attach to remote subvolume of server2<br>volume cli02<br> type protocol/client<br> option transport-type tcp<br>
option remote-host 192.168.240.228 # IP address of the remote brick<br> option remote-subvolume ser022 # name of the remote volume<br>end-volume<br><br>volume afr<br> type cluster/afr<br> subvolumes cli01 cli02<br>
end-volume<br><br>Regards<br><br><div class="gmail_quote">2009/2/13 Krishna Srinivas <span dir="ltr"><<a href="mailto:krishna@zresearch.com">krishna@zresearch.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">On Fri, Feb 13, 2009 at 1:50 PM, Alain Gonzalez <<a href="mailto:alaingonza@gmail.com">alaingonza@gmail.com</a>> wrote:<br>
> I changed vol files, because I need data replicated on three machine (two<br>
> servers and one client). If I changed data on 1 machine, data must be<br>
> changed on the other two machines...<br>
><br>
> My actual vol file:<br>
><br>
> Server1:<br>
><br>
> volume brick<br>
> type storage/posix<br>
> option directory /home/export/<br>
> end-volume<br>
><br>
><br>
> ### Add network serving capability to above brick.<br>
> volume server<br>
> type protocol/server<br>
> option transport-type tcp<br>
> subvolumes brick<br>
> option auth.addr.brick.allow * # Allow access to "brick" volume<br>
> end-volume<br>
><br>
> Server2<br>
><br>
> volume brick<br>
> type storage/posix<br>
> option directory /home/export/<br>
> end-volume<br>
><br>
> ### Add network serving capability to above brick.<br>
> volume server<br>
> type protocol/server<br>
> option transport-type tcp<br>
> subvolumes brick<br>
> option auth.addr.brick.allow * # Allow access to "brick" volume<br>
> end-volume<br>
><br>
> Client:<br>
><br>
> ### Add client feature and attach to remote subvolume of server1<br>
> volume brick1<br>
> type protocol/client<br>
> option transport-type tcp<br>
> option remote-host 192.168.240.227 # IP address of the remote brick<br>
> option remote-subvolume brick # name of the remote volume<br>
> end-volume<br>
><br>
> ### Add client feature and attach to remote subvolume of server2<br>
> volume brick2<br>
> type protocol/client<br>
> option transport-type tcp<br>
> option remote-host 192.168.240.228 # IP address of the remote brick<br>
> option remote-subvolume brick # name of the remote volume<br>
> end-volume<br>
><br>
> volume afr<br>
> type cluster/afr<br>
> subvolumes brick1 brick2<br>
> end-volume<br>
><br>
> Raghavendra G said me that in Glusterfs 2.0 requires posix-locks. I proved<br>
> changed "type storage/posix" for "type features/posix-locks" but not working<br>
> correctly.<br>
><br>
<br>
<br>
</div></div>You need to have a separate "features/locks" translator between<br>
"storage/posix" and "protocol/server" volumes.<br>
</blockquote></div><br><br clear="all"><br>-- <br>Alain Gonzalez<br>