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...<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 changed "type storage/posix" for "type features/posix-locks" but not working correctly.<br><br><div class="gmail_quote">
2009/2/13 Krishna Srinivas <span dir="ltr"><<a href="mailto:krishna@zresearch.com" target="_blank">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;">Alain,<br>
<br>
Are those your actual vol files? just want to confirm.<br>
<div><br>
> option remote-host 192.168.x.x # IP address of server2<br>
<br>
</div>you need to give proper IP address here.<br>
<div><br>
> option auth.ip.brick1.allow *all<br>
> option auth.ip.afr.allow *all<br>
<br>
</div>"*all" is incorrect here.<br>
<br>
If these are not your actual vol files, can you paste them here?<br>
<font color="#888888"><br>
Krishna<br>
</font><div><div></div><div><br>
On Wed, Feb 11, 2009 at 6:04 PM, Alain Gonzalez <<a href="mailto:alaingonza@gmail.com" target="_blank">alaingonza@gmail.com</a>> wrote:<br>
> Hi,<br>
><br>
> I have a problem. I need to replicate data between three machines. Two of<br>
> machines are servers and one is a client.<br>
><br>
> If I change data in client, also changed in the two servers. And if I change<br>
> any data on a server1, also changed in the other server2 and client.<br>
><br>
> I have done tests with the tutorials of glusterfs, but I donīt have good<br>
> results.<br>
><br>
> Someone who can help me?<br>
><br>
> #server1<br>
><br>
> volume brick1<br>
> type storage/posix<br>
> option directory /home/export #created<br>
> end-volume<br>
><br>
> volume brick2<br>
> type protocol/client<br>
> option transport-type tcp/client<br>
><br>
> option remote-host 192.168.x.x # IP address of server2<br>
> option remote-subvolume brick1 # use brick1 on server2<br>
> end-volume<br>
><br>
> volume afr<br>
> type cluster/afr<br>
> subvolumes brick1 brick2<br>
> end-volume<br>
><br>
><br>
> volume server<br>
> type protocol/server<br>
> option transport-type tcp/server<br>
> subvolumes brick1 afr<br>
> option auth.ip.brick1.allow *all<br>
> option auth.ip.afr.allow *all<br>
> end-volumevolume brick1<br>
><br>
><br>
> #server2<br>
><br>
> volume brick1<br>
> type storage/posix<br>
> option directory /home/export #created<br>
> end-volume<br>
><br>
> volume brick2<br>
> type protocol/client<br>
> option transport-type tcp/client<br>
> option remote-host 192.168.x.x # IP address of server1<br>
><br>
> option remote-subvolume brick1 # use brick1 on server1<br>
> end-volume<br>
><br>
> volume afr<br>
> type cluster/afr<br>
> subvolumes brick2 brick1<br>
> end-volume<br>
><br>
> volume server<br>
> type protocol/server<br>
> option transport-type tcp/server<br>
><br>
> subvolumes brick1 afr<br>
> option auth.ip.brick1.allow * #all<br>
> option auth.ip.afr.allow * #all<br>
> end-volume<br>
><br>
> #client<br>
><br>
> volume brick<br>
> type protocol/client<br>
> option transport-type tcp/client # for TCP/IP transport<br>
><br>
> option remote-host 192.168.x.x # IP address of the server ----> IP of<br>
> the server1<br>
> option remote-subvolume afr # name of the remote volume<br>
> end-volume<br>
><br>
> Best Regards<br>
><br>
> --<br>
> Alain Gonzalez<br>
><br>
</div></div><div><div></div><div>> _______________________________________________<br>
> Gluster-devel mailing list<br>
> <a href="mailto:Gluster-devel@nongnu.org" target="_blank">Gluster-devel@nongnu.org</a><br>
> <a href="http://lists.nongnu.org/mailman/listinfo/gluster-devel" target="_blank">http://lists.nongnu.org/mailman/listinfo/gluster-devel</a><br>
><br>
><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Alain Gonzalez<br>