<div dir="ltr"><br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Stas Oskin</b> <span dir="ltr"><<a href="mailto:stas.oskin@gmail.com">stas.oskin@gmail.com</a>></span><br>
Date: 2009/3/9<br>Subject: Re: [Gluster-users] GlusterFS running, but not syncing is done<br>To: Krishna Srinivas ţ<a href="mailto:krishna@zresearch.com">krishna@zresearch.com</a>ţ<br><br><br>Hi.<div><br></div><div>The boxes participating in AFR are running OpenVZ host kernels - can it be related in any way to the issue?</div>
<div><div></div><div class="h5"><div><br></div><div>Regards.<br><br><div class="gmail_quote">2009/3/9 Stas Oskin <span dir="ltr"><<a href="mailto:stas.oskin@gmail.com" target="_blank">stas.oskin@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi.<div><br></div><div>These are my new 2 vol files, one for client and one for server.</div><div><br></div><div>Can you advice if they are correct?</div>
<div><br></div><div>Thanks in advance.</div><div><br>
</div><div>glusterfs.vol (client)</div><div><br></div><div><div><div>## Reference volume "home2" from remote server</div><div>volume home2</div><div> type protocol/client</div><div> option transport-type tcp/client</div>
<div> option remote-host 192.168.253.41 # IP address of remote host</div><div> option remote-subvolume posix-locks-home1 # use home1 on remote host</div><div> option transport-timeout 10 # value in seconds; it should be set relatively low</div>
<div>end-volume</div><div><br></div></div><div><div>### Create automatic file replication</div><div>volume home</div><div> type cluster/afr</div><div> option metadata-self-heal on</div><div> option read-subvolume posix-locks-home1</div>
<div># option favorite-child home2</div></div><div><div> subvolumes posix-locks-home1 home2</div><div>end-volume</div></div></div><div><br></div><div><br></div><div>glusterfsd.vol (server)<br><br></div><div><div>
<div>volume home1</div><div> type storage/posix # POSIX FS translator</div>
<div> option directory /media/storage # Export this directory</div><div>end-volume</div><div><br></div><div>volume posix-locks-home1</div><div> type features/posix-locks</div><div> option mandatory-locks on</div><div>
subvolumes home1</div><div>end-volume</div><div><br></div></div><div><div>### Add network serving capability to above home.</div><div>volume server</div><div> type protocol/server</div><div> option transport-type tcp</div>
<div> subvolumes posix-locks-home1</div>
<div> option auth.addr.posix-locks-home1.allow 192.168.253.41,127.0.0.1 # Allow access to "home1" volume</div><div>end-volume</div><div><br></div></div></div><div><div class="gmail_quote">2009/3/9 Krishna Srinivas <span dir="ltr"><<a href="mailto:krishna@zresearch.com" target="_blank">krishna@zresearch.com</a>></span><div>
<div></div><div><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Stats,<br>
<br>
I think there was nothing changed between rc2 and rc4 that could<br>
affect this functionality.<br>
<br>
Your vol files look fine, i will look into why it is not working.<br>
<br>
Do not use single process as both server and client as we saw issues<br>
related to locking. Can you see if using different processes for<br>
server and client works fine w.r.t replication?<br>
<br>
Also subvolumes list of all AFRs should be in same order (in your case<br>
its interchanged)<br>
<br>
Regards<br>
<font color="#888888">Krishna<br>
</font><div><div></div><div><br>
On Mon, Mar 9, 2009 at 5:44 PM, Stas Oskin <<a href="mailto:stas.oskin@gmail.com" target="_blank">stas.oskin@gmail.com</a>> wrote:<br>
> Actually, I see a new version came out, rc4.<br>
> Any idea if anything related was fixed?<br>
> Regards.<br>
> 2009/3/9 Stas Oskin <<a href="mailto:stas.oskin@gmail.com" target="_blank">stas.oskin@gmail.com</a>><br>
>><br>
>> Hi.<br>
>>><br>
>>> Was it working for your previously? Any other error logs on machine<br>
>>> with afr? what version are you using? If it was working previously<br>
>>> what changed in your setup recently? Can you paste your vol files<br>
>>> (just to be sure)<br>
>><br>
>><br>
>> Nope, it actually my first setup in lab. No errors - it just seems as not<br>
>> synchronizing anything. The version I'm using is the latest one - 2 rc2.<br>
>> Perhaps I need to modify anything else in addition to GlusterFS<br>
>> installation - like file-systems attributes or something?<br>
>> The approach I'm using is the one that was recommended by Kieth over<br>
>> direct emails (Keith, hope you don't mind me posting them :) ).<br>
>> The idea is basically to have single vol file both for client and for<br>
>> server, and to have one glusterfs process doing the job both as client and<br>
>> as server.<br>
>> Thanks for the help.<br>
>> Server 1:<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>
>> ## 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 host<br>
>> option transport-timeout 10 # value in seconds; it should be<br>
>> set relatively low<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 192.168.253.42,127.0.0.1 # Allow<br>
>> access to "home1" volume<br>
>> end-volume<br>
>><br>
>> ### Create automatic file replication<br>
>> volume home<br>
>> type cluster/afr<br>
>> option metadata-self-heal on<br>
>> option read-subvolume posix-locks-home1<br>
>> # option favorite-child home2<br>
>> subvolumes home2 posix-locks-home1<br>
>> end-volume<br>
>><br>
>><br>
>> Server 2:<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>
>> ## 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 host<br>
>> option transport-timeout 10 # value in seconds; it should be<br>
>> set relatively low<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 192.168.253.41,127.0.0.1 # Allow<br>
>> access to "home1" volume<br>
>> end-volume<br>
>><br>
>> ### Create automatic file replication<br>
>> volume home<br>
>> type cluster/afr<br>
>> option metadata-self-heal on<br>
>> option read-subvolume posix-locks-home1<br>
>> # option favorite-child home2<br>
>> subvolumes home2 posix-locks-home1<br>
>> end-volume<br>
</div></div></blockquote></div></div></div></div></blockquote></div></div></div></div></div></div>