<div dir="ltr">Oops, I posted the wrong config for server :).<br><br>Here it is:<br><br>volume home1<br> type storage/posix # POSIX FS translator<br> option directory /media/storage # Export this directory<br>
end-volume<br><br>volume posix-locks-home1<br> type features/posix-locks<br> option mandatory-locks on<br> subvolumes home1<br>end-volume<br><br>### Add network serving capability to above home.<br>volume server<br> type protocol/server<br>
option transport-type tcp<br> subvolumes posix-locks-home1<br> option auth.addr.posix-locks-home1.allow * # Allow access to "home1" volume<br>end-volume<br><br><div class="gmail_quote">2009/4/2 Steve <span dir="ltr"><<a href="mailto:steeeeeveee@gmx.net">steeeeeveee@gmx.net</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;"><br>
-------- Original-Nachricht --------<br>
> Datum: Thu, 2 Apr 2009 13:36:09 +0300<br>
<div><div></div><div class="h5">> Von: Stas Oskin <<a href="mailto:stas.oskin@gmail.com">stas.oskin@gmail.com</a>><br>
> An: Steve <<a href="mailto:steeeeeveee@gmx.net">steeeeeveee@gmx.net</a>><br>
> CC: <a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br>
> Betreff: Re: [Gluster-users] Broken AFR - DU / DF - part 2<br>
<br>
> Nope, only on client - client-sided AFR.<br>
><br>
> The servers are not aware one of each other.<br>
><br>
> Regards.<br>
><br>
> 2009/4/2 Steve <<a href="mailto:steeeeeveee@gmx.net">steeeeeveee@gmx.net</a>><br>
><br>
> ><br>
> > -------- Original-Nachricht --------<br>
> > > Datum: Thu, 2 Apr 2009 13:11:20 +0300<br>
> > > Von: Stas Oskin <<a href="mailto:stas.oskin@gmail.com">stas.oskin@gmail.com</a>><br>
> > > An: Steve <<a href="mailto:steeeeeveee@gmx.net">steeeeeveee@gmx.net</a>><br>
> > > CC: <a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br>
> > > Betreff: Re: [Gluster-users] Broken AFR - DU / DF - part 2<br>
> ><br>
> > > GlusterFS 2 rc7<br>
> > ><br>
> > > Server vol:<br>
> > > ## Reference volume "home1" from remote server<br>
> > > volume home1<br>
> > > type protocol/client<br>
> > > option transport-type tcp/client<br>
> > > option remote-host 192.168.253.41 # IP address of remote host<br>
> > > option remote-subvolume posix-locks-home1 # use home1 on remote<br>
> host<br>
> > > option transport-timeout 10 # value in seconds; it should<br>
> be<br>
> > > set<br>
> > > relatively low<br>
> > > end-volume<br>
> > ><br>
> > > ## Reference volume "home2" from remote server<br>
> > > volume home2<br>
> > > type protocol/client<br>
> > > option transport-type tcp/client<br>
> > > option remote-host 192.168.253.42 # IP address of remote host<br>
> > > option remote-subvolume posix-locks-home1 # use home1 on remote<br>
> host<br>
> > > option transport-timeout 10 # value in seconds; it should<br>
> be<br>
> > > set<br>
> > > relatively low<br>
> > > end-volume<br>
> > ><br>
> > > volume home<br>
> > > type cluster/afr<br>
> > > option metadata-self-heal on<br>
> > > subvolumes home1 home2<br>
> > > end-volume<br>
> > ><br>
</div></div>But this volume here uses AFR in the server vol file. For me this looks like server side AFR.<br>
<div><div></div><div class="h5"><br>
<br>
<br>
> > > Client vol:<br>
> > > ## Reference volume "home1" from remote server<br>
> > > volume home1<br>
> > > type protocol/client<br>
> > > option transport-type tcp/client<br>
> > > option remote-host 192.168.253.42 # IP address of remote host<br>
> > > option remote-subvolume posix-locks-home1 # use home1 on remote<br>
> host<br>
> > > option transport-timeout 10 # value in seconds; it should<br>
> be<br>
> > > set<br>
> > > relatively low<br>
> > > end-volume<br>
> > ><br>
> > > ## Reference volume "home2" from remote server<br>
> > > volume home2<br>
> > > type protocol/client<br>
> > > option transport-type tcp/client<br>
> > > option remote-host 192.168.253.41 # IP address of remote host<br>
> > > option remote-subvolume posix-locks-home1 # use home1 on remote<br>
> host<br>
> > > option transport-timeout 10 # value in seconds; it should<br>
> be<br>
> > > set<br>
> > > relatively low<br>
> > > end-volume<br>
> > ><br>
> > > volume home<br>
> > > type cluster/afr<br>
> > > option metadata-self-heal on<br>
> > > option favorite-child home1<br>
> > > subvolumes home1 home2<br>
> > > end-volume<br>
> > ><br>
> > > volume writebehind<br>
> > > type performance/write-behind<br>
> > > option aggregate-size 128KB<br>
> > > option window-size 1MB<br>
> > > subvolumes home<br>
> > > end-volume<br>
> > ><br>
> > > volume cache<br>
> > > type performance/io-cache<br>
> > > option cache-size 512MB<br>
> > > subvolumes writebehind<br>
> > > end-volume<br>
> > ><br>
> > If I see that right, then you are using AFR on the server and on the<br>
> > client. Right?<br>
> > --<br>
> > Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate +<br>
> > Telefonanschluss für nur 17,95 Euro/mtl.!*<br>
> > <a href="http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a" target="_blank">http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a</a><br>
> ><br>
> > _______________________________________________<br>
> > Gluster-users mailing list<br>
> > <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
> > <a href="http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users" target="_blank">http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users</a><br>
> ><br>
<br>
</div></div>--<br>
<div class="im">Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: <a href="http://www.gmx.net/de/go/multimessenger01" target="_blank">http://www.gmx.net/de/go/multimessenger01</a><br>
<br>
_______________________________________________<br>
</div><div><div></div><div class="h5">Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users" target="_blank">http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users</a><br>
</div></div></blockquote></div></div>