<div dir="ltr">Hi.<br><br>It's exactly same that you posted earlier:<br><br>client.vol<br>----<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 host<br> option transport-timeout 10 # value in seconds; it should be set 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 host<br> option transport-timeout 10 # value in seconds; it should be set 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><br>server.vol<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>Regards.<br><br><div class="gmail_quote">2009/3/15 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;">Can you paste your client vol file? and the command you used to mount<br>
the glusterfs?<br>
<font color="#888888"><br>
Krishna<br>
</font><div><div></div><div class="h5"><br>
On Sun, Mar 15, 2009 at 5:57 PM, Stas Oskin <<a href="mailto:stas.oskin@gmail.com">stas.oskin@gmail.com</a>> wrote:<br>
> Hi.<br>
><br>
> Just tried this, server works but the client fails.<br>
><br>
> Here is the error that the client prints:<br>
><br>
> 2009-03-15 14:21:51 E [glusterfsd.c:551:glusterfs_graph_init] glusterfs: no<br>
> valid translator loaded at the top or no mount point given. exiting<br>
> 2009-03-15 14:21:51 E [glusterfsd.c:1127:main] glusterfs: translator<br>
> initialization failed. exiting<br>
><br>
><br>
> Two possible reasons I can think of:<br>
><br>
> 1) The volume is always home1 on both the servers, while in client file both<br>
> home1 and home2 are referenced. Shouldn't the .42 have home2 defined as it's<br>
> volume? Or it doesn't matter, as home2 is client-only volume label?<br>
><br>
> 2) The "/media/directory" is a regular directory on disk. Should it be a<br>
> mount or something else?<br>
><br>
> 3) I'm using stock kernel without any modifications. Nor I did any changes<br>
> to filesystems for extended attributes (using ext3). Would fuse work without<br>
> any problems?<br>
><br>
> Thanks!<br>
><br>
> 2009/3/12 Krishna Srinivas <<a href="mailto:krishna@zresearch.com">krishna@zresearch.com</a>><br>
>><br>
>> server.vol :<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"<br>
>> volume<br>
>> end-volume<br>
>><br>
>> ----------<br>
>><br>
>> client.vol:<br>
>> ---------<br>
>><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 host<br>
>> option transport-timeout 10 # value in seconds; it should<br>
>> be set 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 host<br>
>> option transport-timeout 10 # value in seconds; it should<br>
>> be set 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>
>> --------<br>
>><br>
>> Make sure the IP addresses are correct.<br>
>> You can use the same server.vol and client.vol for both the machines.<br>
>> (assuming you have backend directory names same)<br>
>><br>
>> Krishna<br>
>><br>
>> On Thu, Mar 12, 2009 at 8:28 PM, Stas Oskin <<a href="mailto:stas.oskin@gmail.com">stas.oskin@gmail.com</a>> wrote:<br>
>> > Hi.<br>
>> ><br>
>> > Did you mean to change their order to become something like this?<br>
>> ><br>
>> > Otherwise can you please just post the correct version? I'm not quite<br>
>> > familiar with the syntax, and will appreciate an example I can work and<br>
>> > learn from.<br>
>> ><br>
>> > Thanks!<br>
>> ><br>
>> ><br>
>> > glusterfs.vol (client)<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 posix-locks-home1 home2<br>
>> > end-volume<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 be<br>
>> > set<br>
>> > relatively low<br>
>> > end-volume<br>
>> ><br>
>> > glusterfsd.vol (server)<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 #<br>
>> > Allow<br>
>> > access to "home1" volume<br>
>> > end-volume<br>
>> > volume posix-locks-home1<br>
>> > type features/posix-locks<br>
>> > option mandatory-locks on<br>
>> > subvolumes home1<br>
>> > end-volume<br>
>> > volume home1<br>
>> > type storage/posix # POSIX FS translator<br>
>> > option directory /media/storage # Export this directory<br>
>> > end-volume<br>
>> > Regards.<br>
>> ><br>
>> > 2009/3/12 Krishna Srinivas <<a href="mailto:krishna@zresearch.com">krishna@zresearch.com</a>><br>
>> >><br>
>> >> Hi Stats,<br>
>> >> Excuse me for missing out on this mail.<br>
>> >><br>
>> >> Your vol files for having 2 servers and 2 clients are incorrect.<br>
>> >><br>
>> >> on server vol (both the machines) you need to have:<br>
>> >> protocol/server -> features/locks -> storage/posix<br>
>> >><br>
>> >> On client vol (both the machines) you need to have:<br>
>> >> cluster/afr -> (two protocol/clients)<br>
>> >><br>
>> >> each of the protocol/clients connect to each of the servers.<br>
>> >><br>
>> >> You would use the client vol to mount the glusterfs.<br>
>> >><br>
>> >> Let us know if you still face problems.<br>
>> >><br>
>> >> Krishna<br>
>> >><br>
>> >> On Tue, Mar 10, 2009 at 1:32 AM, Stas Oskin <<a href="mailto:stas.oskin@gmail.com">stas.oskin@gmail.com</a>><br>
>> >> wrote:<br>
>> >> > Hi.<br>
>> >> > The boxes participating in AFR are running OpenVZ host kernels - can<br>
>> >> > it<br>
>> >> > be<br>
>> >> > related in any way to the issue?<br>
>> >> > Regards.<br>
>> >> ><br>
>> >> > 2009/3/9 Stas Oskin <<a href="mailto:stas.oskin@gmail.com">stas.oskin@gmail.com</a>><br>
>> >> >><br>
>> >> >> Hi.<br>
>> >> >> These are my new 2 vol files, one for client and one for server.<br>
>> >> >> Can you advice if they are correct?<br>
>> >> >> Thanks in advance.<br>
>> >> >> glusterfs.vol (client)<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 relatively low<br>
>> >> >> end-volume<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 posix-locks-home1 home2<br>
>> >> >> end-volume<br>
>> >> >><br>
>> >> >> glusterfsd.vol (server)<br>
>> >> >><br>
>> >> >> volume home1<br>
>> >> >> type storage/posix # POSIX FS translator<br>
>> >> >> option directory /media/storage # Export this directory<br>
>> >> >> end-volume<br>
>> >> >> volume posix-locks-home1<br>
>> >> >> type features/posix-locks<br>
>> >> >> option mandatory-locks on<br>
>> >> >> subvolumes home1<br>
>> >> >> end-volume<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 #<br>
>> >> >> Allow<br>
>> >> >> access to "home1" volume<br>
>> >> >> end-volume<br>
>> >> >> 2009/3/9 Krishna Srinivas <<a href="mailto:krishna@zresearch.com">krishna@zresearch.com</a>><br>
>> >> >>><br>
>> >> >>> 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<br>
>> >> >>> 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<br>
>> >> >>> case<br>
>> >> >>> its interchanged)<br>
>> >> >>><br>
>> >> >>> Regards<br>
>> >> >>> Krishna<br>
>> >> >>><br>
>> >> >>> On Mon, Mar 9, 2009 at 5:44 PM, Stas Oskin <<a href="mailto:stas.oskin@gmail.com">stas.oskin@gmail.com</a>><br>
>> >> >>> 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">stas.oskin@gmail.com</a>><br>
>> >> >>> >><br>
>> >> >>> >> Hi.<br>
>> >> >>> >>><br>
>> >> >>> >>> Was it working for your previously? Any other error logs on<br>
>> >> >>> >>> machine<br>
>> >> >>> >>> with afr? what version are you using? If it was working<br>
>> >> >>> >>> previously<br>
>> >> >>> >>> what changed in your setup recently? Can you paste your vol<br>
>> >> >>> >>> files<br>
>> >> >>> >>> (just to be sure)<br>
>> >> >>> >><br>
>> >> >>> >><br>
>> >> >>> >> Nope, it actually my first setup in lab. No errors - it just<br>
>> >> >>> >> seems<br>
>> >> >>> >> as<br>
>> >> >>> >> not<br>
>> >> >>> >> synchronizing anything. The version I'm using is the latest one<br>
>> >> >>> >> - 2<br>
>> >> >>> >> 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<br>
>> >> >>> >> 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<br>
>> >> >>> >> and<br>
>> >> >>> >> for<br>
>> >> >>> >> server, and to have one glusterfs process doing the job both as<br>
>> >> >>> >> client<br>
>> >> >>> >> 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<br>
>> >> >>> >> host<br>
>> >> >>> >> option remote-subvolume posix-locks-home1 # use home1 on<br>
>> >> >>> >> remote<br>
>> >> >>> >> host<br>
>> >> >>> >> option transport-timeout 10 # value in seconds; it<br>
>> >> >>> >> should<br>
>> >> >>> >> 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<br>
>> >> >>> >> 192.168.253.42,127.0.0.1<br>
>> >> >>> >> #<br>
>> >> >>> >> 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<br>
>> >> >>> >> host<br>
>> >> >>> >> option remote-subvolume posix-locks-home1 # use home1 on<br>
>> >> >>> >> remote<br>
>> >> >>> >> host<br>
>> >> >>> >> option transport-timeout 10 # value in seconds; it<br>
>> >> >>> >> should<br>
>> >> >>> >> 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<br>
>> >> >>> >> 192.168.253.41,127.0.0.1<br>
>> >> >>> >> #<br>
>> >> >>> >> 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>
><br>
</div></div></blockquote></div></div>